← previous blocknext block →recent activity
Analyzing
Block #86,234,574
18 transactions · 14 stateful · 2026-07-07 17:10:32 UTC
Parallelism
78/100
Blocked
21%
Avg conflicts / tx
0.28
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,234,574 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w15w06w214w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x5da225de…e8b9
0x065c9d…c394
6 touches
3 conflicts
0x00000000…003d
0x065c9d…c394
6 touches
3 conflicts
0xdfa159d0…1576
0x065c9d…c394
6 touches
3 conflicts
0x99ba92dd…3086
0x065c9d…c394
5 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x9bd2e3c1…3181
0x065c9d…c394
4 touches
1 conflict
0x5046e213…7ead
0xd32edf…ff58
3 touches
1 conflict
0x247929d5…e5c4
0x065c9d…c394
3 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
3 conflicts on slot 0x5da225dea5…b6e8b9
Audit this contract →
← previous block·next block →recent activity