just means it took that long for twetch to broadcast AND for BB to see the tx
YOU are not interacting with the chain yourself,
things can take time for whatever reason
Post by 1JcRRk…79XP
so when was the post (are you even listening) made 6:27 here or as recorded by the immutable blockchain 6:31
Ironshirtz 2w
computers very easily have 10 seconds time difference
even when they sync to the same clock
time is not perfect across the internet
data transfer is not instant
What the chain says
- Block
- 967 553
- Time
- 2026-09-20T06:42:14Z
- Signer
- 1JcRRksn5vgR4266FX7Dyx5xyZq28G79XP
- App
- twetch
- Type
- reply
- Content type
- text/markdown
Fields the transaction did not carry are omitted. Open the payload to see the bytes as stored.
Signed by
1JcRRksn5vgR4266FX7Dyx5xyZq28G79XP UnverifiedReplies (17)
post could be first posted on twetch at 6:27,
the tx gets broadcast at some point
hits the mempool
then BB picks up the tx at 6:31
do a test post
check your phone time when posting
then from the post click view on chain and check the time difference
does your phone time match twetch or BB ?
oh boy mempool must be alcohol
twetch#15875 6.7y
no-one ever mentions He only admits to loving you when He is drunk
for twetch broadcasting tx's is not a duper priority TBH
or should not be
I even think it would be nice to have a 30 second edit time delay before comment gets broadcast, just for typos
but then
I also don't understand why twetch are still chasing social on chain instead of crypto social
I even think it would be nice to have a 17 min time delay on when an entry was actually made.
i thought UTC was +12 @5937
This thread is longer than one page shows. Open a reply to see what follows it.