← previous blocknext block →recent activity
Analyzing
Block #86,669,576
55 transactions · 43 stateful · 2026-07-09 17:39:43 UTC
Parallelism
73/100
Blocked
60%
Avg conflicts / tx
2.18
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,669,576 · 55 txs across 15 waves · depth 15
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
5w011w012w114w015w116w018w119w220w321w422w523w624w725w826w927w1028w1129w1232w134w139w243w245w346w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x03fb27fd…0c06
0x34b655…2a6f
20 touches
45 conflicts
0x922c7ebd…6600
0xc8689a…ee79
20 touches
45 conflicts
0x9f40a209…1193
0x34b655…2a6f
20 touches
45 conflicts
0xb25fa8e2…c9ef
0x34b655…2a6f
20 touches
45 conflicts
0xd786a4f1…12d6
0x34b655…2a6f
20 touches
45 conflicts
0xdfe311f9…a651
0x34b655…2a6f
20 touches
45 conflicts
0x025393f0…8bab
0x34b655…2a6f
20 touches
45 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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity