← previous blocknext block →recent activity
Analyzing
Block #73,393,420
22 transactions · 16 stateful · 2026-05-09 05:22:05 UTC
Parallelism
86/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,393,420 · 22 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w04w06w07w08w19w210w111w213w118w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xab3526…fa38
6 touches
3 conflicts
0x4d87512b…897c
0x065c9d…c394
6 touches
3 conflicts
0xe038916c…b1be
0x2a68ba…90c5
6 touches
3 conflicts
0xe11cac9f…0c38
0xd32edf…ff58
5 touches
3 conflicts
0x48212ae4…afec
0x065c9d…c394
4 touches
1 conflict
0x4bfdd5fb…d52b
0x065c9d…c394
4 touches
1 conflict
0x2e2214a9…fe0d
0x8e764f…e322
4 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity