← previous blocknext block →recent activity
Analyzing
Block #86,823,629
17 transactions · 14 stateful · 2026-07-10 10:48:48 UTC
Parallelism
76/100
Blocked
43%
Avg conflicts / tx
0.65
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,823,629 · 17 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
1w02w14w28w09w010w111w212w216w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x889f0954…da52
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xe1719e7b…617e
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…001b
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002b
0x1b6862…e19c
4 touches
1 conflict
0xb0e4f69d…34e4
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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: Perpl
3 conflicts on slot 0x889f0954f9…86da52
Audit this contract →
← previous block·next block →recent activity