← previous blocknext block →recent activity
Analyzing
Block #73,270,446
22 transactions · 13 stateful · 2026-05-08 15:43:57 UTC
Parallelism
86/100
Blocked
23%
Avg conflicts / tx
0.18
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #73,270,446 · 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
1w02w14w05w116w017w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
4 touches
1 conflict
0x0b390c61…dc07
0x065c9d…c394
4 touches
1 conflict
0xf2f76ab3…623e
0x2a68ba…90c5
4 touches
1 conflict
0x00000000…0002
0xab3526…fa38
4 touches
1 conflict
0x7fd7d999…d1bd
0xd32edf…ff58
3 touches
1 conflict
0x6780a542…c071
0x065c9d…c394
2 touches
0 conflicts
0xa5250c08…d289
0x065c9d…c394
2 touches
0 conflicts
0xb135907c…5b3a
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