← previous blocknext block →recent activity
Analyzing
Block #77,355,913
17 transactions · 13 stateful · 2026-05-27 14:02:25 UTC
Parallelism
82/100
Blocked
23%
Avg conflicts / tx
0.24
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #77,355,913 · 17 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w16w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0xb2fc5299…9613
0x065c9d…c394
3 touches
1 conflict
0xb29f0e36…b297
0x065c9d…c394
2 touches
0 conflicts
0xb706e731…dd07
0x065c9d…c394
2 touches
0 conflicts
0xb833cc91…b726
0x065c9d…c394
2 touches
0 conflicts
0xcc8faac2…c766
0x065c9d…c394
2 touches
0 conflicts
0xe5293c7d…3de7
0x065c9d…c394
2 touches
0 conflicts
What's blocking what?
Click any transaction in the timeline or graph to see which storage slots forced it to wait, and which later transactions it blocked.
The bottleneck
Throughput-killer: Kuru Exchange: Market-MON/USDC
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity