← previous blocknext block →recent activity
Analyzing
Block #77,357,767
16 transactions · 9 stateful · 2026-05-27 14:14:46 UTC
Parallelism
75/100
Blocked
33%
Avg conflicts / tx
0.38
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #77,357,767 · 16 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w16w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
8 touches
6 conflicts
0x3880a163…c8cf
0x065c9d…c394
4 touches
1 conflict
0xe23570a8…269d
0x065c9d…c394
3 touches
1 conflict
0x433287e5…6de5
0x065c9d…c394
2 touches
0 conflicts
0x44bbc30f…cce9
0x065c9d…c394
2 touches
0 conflicts
0xaa89a34b…57aa
0x065c9d…c394
2 touches
0 conflicts
0xb77f456c…3855
0x065c9d…c394
2 touches
0 conflicts
0xcfb145b4…1b86
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
6 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity