← previous blocknext block →recent activity
Analyzing
Block #72,431,149
9 transactions · 7 stateful · 2026-05-04 18:34:44 UTC
Parallelism
78/100
Blocked
14%
Avg conflicts / tx
0.11
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #72,431,149 · 9 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
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x8dd72e73…02e4
0x065c9d…c394
4 touches
1 conflict
0xc332170c…6f97
0x065c9d…c394
3 touches
1 conflict
0xfcffa96f…bf8b
0x065c9d…c394
3 touches
1 conflict
0x31e9ff2a…7dba
0x065c9d…c394
2 touches
0 conflicts
0x5ffc87ee…43bc
0x065c9d…c394
2 touches
0 conflicts
0x7124934d…4c70
0x065c9d…c394
2 touches
0 conflicts
0x7d25b4ea…b468
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