← previous blocknext block →recent activity
Analyzing
Block #86,451,600
79 transactions · 60 stateful · 2026-07-08 17:20:06 UTC
Parallelism
73/100
Blocked
78%
Avg conflicts / tx
3.01
Longest chain
21 deep
Execution timeline
did this block parallelize well?
view
block #86,451,600 · 79 txs across 21 waves · depth 21
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
wave w16
wave w17
wave w18
wave w19
wave w20
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w35w46w57w68w79w810w319w452w9
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
28 touches
91 conflicts
0x13ff6f87…dfc9
0xd32edf…ff58
19 touches
45 conflicts
0x727fbce7…0c80
0x34b655…2a6f
16 touches
28 conflicts
0x04105a34…6eea
0x34b655…2a6f
16 touches
28 conflicts
0xc368d7fd…aaec
0x34b655…2a6f
16 touches
28 conflicts
0x922c7ebd…6600
0xc8689a…ee79
16 touches
28 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
16 touches
28 conflicts
0x5d7f309d…5145
0x34b655…2a6f
16 touches
28 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
91 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity