← previous blocknext block →recent activity
Analyzing
Block #73,654,219
22 transactions · 18 stateful · 2026-05-10 10:19:36 UTC
Parallelism
55/100
Blocked
67%
Avg conflicts / tx
1.27
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #73,654,219 · 22 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w06w27w38w410w511w612w715w816w919w120w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xc5ceeb8e…27d8
0xd32edf…ff58
9 touches
10 conflicts
0x529acb6a…fcc6
0x065c9d…c394
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
6 touches
3 conflicts
0x7f81fb82…633e
0x065c9d…c394
6 touches
3 conflicts
0x4073012d…87f9
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xf2438038…5fa7
0x34b655…2a6f
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
10 conflicts on slot 0x0000000000…00003d
Audit this contract →
← previous block·next block →recent activity