← previous blocknext block →recent activity
Analyzing
Block #73,026,657
21 transactions · 16 stateful · 2026-05-07 12:41:54 UTC
Parallelism
76/100
Blocked
38%
Avg conflicts / tx
0.71
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #73,026,657 · 21 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w29w010w112w315w316w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0x6f08361d…bda6
0x065c9d…c394
6 touches
3 conflicts
0xf537eaa0…73c8
0x065c9d…c394
6 touches
3 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf68d26b3…6b9c
0x065c9d…c394
5 touches
3 conflicts
0xa61ad11e…5dc1
0xd32edf…ff58
5 touches
3 conflicts
0x326856a5…8250
0x065c9d…c394
5 touches
3 conflicts
0x3dbc935d…d070
0x065c9d…c394
5 touches
3 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
3 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity