← previous blocknext block →recent activity
Analyzing
Block #86,667,403
38 transactions · 34 stateful · 2026-07-09 17:25:13 UTC
Parallelism
79/100
Blocked
56%
Avg conflicts / tx
1.16
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,667,403 · 38 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
1w02w13w24w36w47w28w19w010w111w412w519w020w123w024w125w228w229w531w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x979a1f2e…b342
0xd32edf…ff58
9 touches
10 conflicts
0xa7013be2…c0a8
0x34b655…2a6f
8 touches
6 conflicts
0x3559c176…9fe1
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0018
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0x394c3833…b4a7
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity