← previous blocknext block →recent activity
Analyzing
Block #71,688,908
8 transactions · 7 stateful · 2026-05-01 08:04:27 UTC
Parallelism
75/100
Blocked
14%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #71,688,908 · 8 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcdd22abc…3837
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x47b807a2…3307
0x065c9d…c394
4 touches
1 conflict
0xc7784a31…8269
0x065c9d…c394
4 touches
1 conflict
0x810d0c79…266b
0x065c9d…c394
3 touches
1 conflict
0x1db757bb…a3be
0x065c9d…c394
3 touches
1 conflict
0x9b1195ca…5c5a
0x065c9d…c394
3 touches
1 conflict
0xc52cef31…6eae
0x065c9d…c394
3 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
1 conflict on slot 0xcdd22abc78…c53837
Audit this contract →
← previous block·next block →recent activity