← previous blocknext block →recent activity
Analyzing
Block #72,431,187
7 transactions · 6 stateful · 2026-05-04 18:34: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,431,187 · 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
1w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcf41bef6…b6fd
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xf6667f48…e7ff
0x065c9d…c394
3 touches
1 conflict
0x16c0eeb6…c088
0x065c9d…c394
2 touches
0 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
2 touches
0 conflicts
0x6d474dd4…3f2e
0x065c9d…c394
2 touches
0 conflicts
0x90a6030d…08e3
0x065c9d…c394
2 touches
0 conflicts
0x9f7a2132…643b
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 0xcf41bef6c3…6fb6fd
Audit this contract →
← previous block·next block →recent activity