← previous blocknext block →recent activity
Analyzing
Block #72,431,338
8 transactions · 7 stateful · 2026-05-04 18:36:00 UTC
Parallelism
75/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,431,338 · 8 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
2w03w04w17w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8a35acfb…d1ad
0x8d66a4…3095
4 touches
1 conflict
0x96504a63…52d2
0x8d66a4…3095
4 touches
1 conflict
0x24216e94…9055
0x065c9d…c394
2 touches
0 conflicts
0xac78986d…50ad
0x065c9d…c394
2 touches
0 conflicts
0xb9adf07e…02c4
0x065c9d…c394
2 touches
0 conflicts
0xc4e1abb5…57b5
0x065c9d…c394
2 touches
0 conflicts
0xeb8469d1…1e2d
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 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity