← previous blocknext block →recent activity
Analyzing
Block #72,295,869
6 transactions · 6 stateful · 2026-05-04 03:33:26 UTC
Parallelism
67/100
Blocked
17%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,295,869 · 6 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
1w05w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd3db58c0…0929
0x065c9d…c394
4 touches
1 conflict
0x24968e6d…0132
0x065c9d…c394
4 touches
1 conflict
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0xfae64e8b…5349
0x065c9d…c394
4 touches
1 conflict
0xe0a47ba7…770e
0x065c9d…c394
3 touches
1 conflict
0xc3e03394…7165
0x065c9d…c394
3 touches
1 conflict
0x69c32d0c…be14
0x065c9d…c394
3 touches
1 conflict
0xe6429bff…4750
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 0xd3db58c0d9…8d0929
Audit this contract →
← previous block·next block →recent activity