← previous blocknext block →recent activity
Analyzing
Block #72,575,263
8 transactions · 8 stateful · 2026-05-05 10:34:24 UTC
Parallelism
75/100
Blocked
13%
Avg conflicts / tx
0.13
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,575,263 · 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
2w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x150d78cc…8d1e
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x5ca0f1f4…d2bd
0x065c9d…c394
4 touches
1 conflict
0x6c3d1fed…de77
0x065c9d…c394
3 touches
1 conflict
0x90dc0fdb…4824
0x065c9d…c394
3 touches
1 conflict
0x0aac143c…6e38
0x065c9d…c394
3 touches
1 conflict
0x3dd1ff9c…68ae
0x065c9d…c394
3 touches
1 conflict
0xbbee74c2…567a
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 0x150d78cc32…968d1e
Audit this contract →
← previous block·next block →recent activity