← previous blocknext block →recent activity
Analyzing
Block #86,683,819
17 transactions · 14 stateful · 2026-07-09 19:14:50 UTC
Parallelism
71/100
Blocked
36%
Avg conflicts / tx
0.47
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,683,819 · 17 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w28w09w113w314w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd1fe26e6…8d31
0x34b655…2a6f
8 touches
6 conflicts
0x1d12e23a…dee0
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
6 touches
3 conflicts
0x2c2a63c5…96c8
0x34b655…2a6f
6 touches
3 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
6 touches
3 conflicts
0x63c900f4…2600
0x34b655…2a6f
6 touches
3 conflicts
0x664bab3b…a072
0x34b655…2a6f
6 touches
3 conflicts
0x727fbce7…0c80
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: Perpl
6 conflicts on slot 0xd1fe26e65e…678d31
Audit this contract →
← previous block·next block →recent activity