← previous blocknext block →recent activity
Analyzing
Block #72,426,225
8 transactions · 8 stateful · 2026-05-04 18:02:00 UTC
Parallelism
63/100
Blocked
25%
Avg conflicts / tx
0.38
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,426,225 · 8 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
1w04w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
4 touches
1 conflict
0x31e9ff2a…7dba
0x065c9d…c394
3 touches
1 conflict
0x6d0658d3…5c2c
0x065c9d…c394
3 touches
1 conflict
0x3414f9b0…771f
0x065c9d…c394
2 touches
0 conflicts
0x871b2fea…8767
0x065c9d…c394
2 touches
0 conflicts
0x904759e0…77da
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