← previous blocknext block →recent activity
Analyzing
Block #86,708,475
16 transactions · 13 stateful · 2026-07-09 21:59:17 UTC
Parallelism
69/100
Blocked
46%
Avg conflicts / tx
0.81
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,708,475 · 16 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
1w02w13w24w37w09w410w113w015w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x22e0cc1d…ad0d
0x34b655…2a6f
10 touches
10 conflicts
0x3483ab79…8ed3
0x34b655…2a6f
8 touches
6 conflicts
0x4c7a4dca…ad0c
0x34b655…2a6f
8 touches
6 conflicts
0x548145a9…cfce
0x34b655…2a6f
8 touches
6 conflicts
0x63b15849…80b2
0x34b655…2a6f
8 touches
6 conflicts
0x63c900f4…2600
0x34b655…2a6f
8 touches
6 conflicts
0x9138a113…0d5f
0x34b655…2a6f
8 touches
6 conflicts
0x922c7ebd…6600
0xc8689a…ee79
8 touches
6 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
10 conflicts on slot 0x22e0cc1d4a…90ad0d
Audit this contract →
← previous block·next block →recent activity