← previous blocknext block →recent activity
Analyzing
Block #86,790,042
48 transactions · 41 stateful · 2026-07-10 07:04:08 UTC
Parallelism
83/100
Blocked
56%
Avg conflicts / tx
1.13
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,790,042 · 48 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w26w17w29w411w314w415w536w637w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…003d
0x065c9d…c394
10 touches
10 conflicts
0xcccf0a99…8388
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…001a
0x1b6862…e19c
8 touches
6 conflicts
0xb6ed530c…d450
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…002a
0x1b6862…e19c
8 touches
6 conflicts
0xa87df366…081f
0x1b6862…e19c
8 touches
6 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
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 0x92385428ad…dc6941
Audit this contract →
← previous block·next block →recent activity