← previous blocknext block →recent activity
Analyzing
Block #72,212,977
6 transactions · 6 stateful · 2026-05-03 18:16:27 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,212,977 · 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
1w04w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb4d1cf96…e34d
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x9b762f2c…7519
0x065c9d…c394
3 touches
1 conflict
0x54778081…80c8
0x065c9d…c394
3 touches
1 conflict
0x4ff1c451…b192
0x065c9d…c394
2 touches
0 conflicts
0x8e6ad6e7…f577
0x065c9d…c394
2 touches
0 conflicts
0xb24a1aff…ef9f
0x065c9d…c394
2 touches
0 conflicts
0xbf03ded8…62dd
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 0xb4d1cf9661…c9e34d
Audit this contract →
← previous block·next block →recent activity