← previous blocknext block →recent activity
Analyzing
Block #72,973,942
15 transactions · 13 stateful · 2026-05-07 06:51:02 UTC
Parallelism
80/100
Blocked
38%
Avg conflicts / tx
0.6
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #72,973,942 · 15 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
2w03w15w06w19w010w112w214w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x7f189cf6…afab
0x065c9d…c394
6 touches
3 conflicts
0xce7bfe5e…5e58
0x065c9d…c394
6 touches
3 conflicts
0x41f7d83d…143e
0x34b655…2a6f
6 touches
3 conflicts
0x85a88798…f85e
0x34b655…2a6f
6 touches
3 conflicts
0xf4730a2d…3538
0x34b655…2a6f
6 touches
3 conflicts
0x3e535260…1fb1
0xd32edf…ff58
5 touches
3 conflicts
0x085df2c1…305a
0x34b655…2a6f
4 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity