← previous blocknext block →recent activity
Analyzing
Block #86,711,185
24 transactions · 20 stateful · 2026-07-09 22:17:22 UTC
Parallelism
79/100
Blocked
50%
Avg conflicts / tx
0.96
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #86,711,185 · 24 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
1w02w13w25w37w08w19w010w411w212w113w317w323w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x30ded6ec…3424
0x34b655…2a6f
8 touches
6 conflicts
0xf41abe75…cfcc
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0013
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0xd25997d0…a684
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x30ded6ecaf…443424
Audit this contract →
← previous block·next block →recent activity