← previous blocknext block →recent activity
Analyzing
Block #73,807,709
20 transactions · 18 stateful · 2026-05-11 03:34:55 UTC
Parallelism
65/100
Blocked
56%
Avg conflicts / tx
1.4
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #73,807,709 · 20 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w17w08w19w210w312w213w314w315w416w517w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
14 touches
21 conflicts
0x4d87512b…897c
0x065c9d…c394
8 touches
6 conflicts
0x60f7fbaf…bd58
0x34b655…2a6f
8 touches
6 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
6 touches
3 conflicts
0xab41bf9c…66a9
0x34b655…2a6f
6 touches
3 conflicts
0xb378025c…30cf
0x34b655…2a6f
6 touches
3 conflicts
0xedb848fe…6534
0x34b655…2a6f
6 touches
3 conflicts
0xc6417de0…2191
0xc8689a…ee79
6 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
21 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity