← previous blocknext block →recent activity
Analyzing
Block #72,224,238
12 transactions · 9 stateful · 2026-05-03 19:32:01 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,224,238 · 12 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
2w04w16w09w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x2d10a2de…811f
0x065c9d…c394
4 touches
1 conflict
0x00000000…0002
0x7e9d3a…9fda
4 touches
1 conflict
0xb90c5fb2…f6e5
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x41755291…977f
0x065c9d…c394
4 touches
1 conflict
0x5a176085…53b0
0x065c9d…c394
3 touches
1 conflict
0x933f30e1…4539
0x065c9d…c394
3 touches
1 conflict
0xe1f76607…fbb1
0x065c9d…c394
3 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
1 conflict on slot 0x2d10a2de2a…08811f
Audit this contract →
← previous block·next block →recent activity