← previous blocknext block →recent activity
Analyzing
Block #72,572,922
6 transactions · 5 stateful · 2026-05-05 10:18:47 UTC
Parallelism
67/100
Blocked
20%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,572,922 · 6 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
1w02w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8ca64ffc…f0c0
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x444c7077…9c50
0x065c9d…c394
3 touches
1 conflict
0x9d0da87a…6540
0x065c9d…c394
3 touches
1 conflict
0x668a0994…ea96
0x065c9d…c394
2 touches
0 conflicts
0x76fffe34…f3b0
0x065c9d…c394
2 touches
0 conflicts
0x8d20ceeb…877c
0x065c9d…c394
2 touches
0 conflicts
0x9a3fd26c…03f7
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
1 conflict on slot 0x8ca64ffc9a…56f0c0
Audit this contract →
← previous block·next block →recent activity