← previous blocknext block →recent activity
Analyzing
Block #72,572,204
7 transactions · 6 stateful · 2026-05-05 10:13:59 UTC
Parallelism
71/100
Blocked
17%
Avg conflicts / tx
0.14
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,572,204 · 7 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb616ad12…0f16
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xd512adf7…36e3
0x065c9d…c394
3 touches
1 conflict
0xc5acff22…e20c
0x065c9d…c394
3 touches
1 conflict
0x1c1cefc0…267b
0x065c9d…c394
2 touches
0 conflicts
0x1c6ecbfb…ee06
0x065c9d…c394
2 touches
0 conflicts
0x73c51b8a…39ae
0x065c9d…c394
2 touches
0 conflicts
0x80a9c7f5…f7c9
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 0xb616ad123d…5a0f16
Audit this contract →
← previous block·next block →recent activity