← previous blocknext block →recent activity
Analyzing
Block #73,434,453
16 transactions · 14 stateful · 2026-05-09 09:55:10 UTC
Parallelism
63/100
Blocked
43%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #73,434,453 · 16 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w17w08w19w210w311w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xf537eaa0…73c8
0x065c9d…c394
4 touches
1 conflict
0xbec0403f…342e
0xd32edf…ff58
3 touches
1 conflict
0x00000000…0002
0x094452…0a09
2 touches
0 conflicts
0x00000000…0004
0x094452…0a09
2 touches
0 conflicts
0x00000000…00d6
0x094452…0a09
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
15 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity