← previous blocknext block →recent activity
Analyzing
Block #73,795,952
15 transactions · 13 stateful · 2026-05-11 02:15:58 UTC
Parallelism
67/100
Blocked
62%
Avg conflicts / tx
0.93
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,795,952 · 15 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w14w27w18w29w310w111w414w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x529acb6a…fcc6
0x065c9d…c394
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0x468c69b1…af11
0x8d66a4…3095
6 touches
3 conflicts
0x8a35acfb…d1ae
0x8d66a4…3095
6 touches
3 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
4 touches
1 conflict
0x8a85cf3d…2868
0x34b655…2a6f
4 touches
1 conflict
0xdf7899c0…c53a
0x34b655…2a6f
4 touches
1 conflict
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