← previous blocknext block →recent activity
Analyzing
Block #71,045,162
22 transactions · 20 stateful · 2026-04-28 08:33:29 UTC
Parallelism
55/100
Blocked
55%
Avg conflicts / tx
1.32
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #71,045,162 · 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
1w02w03w15w06w07w18w29w310w411w512w613w014w715w816w921w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…003d
0x065c9d…c394
12 touches
15 conflicts
0x5c8c6ab6…dc36
0x065c9d…c394
8 touches
6 conflicts
0x00000000…003d
0x131a2e…0da9
8 touches
6 conflicts
0x046a928e…0012
0x2a68ba…90c5
8 touches
6 conflicts
0xffe431af…8faa
0x065c9d…c394
6 touches
3 conflicts
0x00000000…0002
0xb857c1…9be1
4 touches
1 conflict
0xb378025c…30cf
0x34b655…2a6f
4 touches
1 conflict
0xffe431af…8faa
0x131a2e…0da9
4 touches
1 conflict
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