← previous blocknext block →recent activity
Analyzing
Block #86,807,576
53 transactions · 44 stateful · 2026-07-10 09:01:17 UTC
Parallelism
62/100
Blocked
73%
Avg conflicts / tx
2.75
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,807,576 · 53 txs across 20 waves · depth 20
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w15w26w07w19w210w312w418w019w121w022w123w242w443w247w348w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0xec7fe04a…3c56
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
10 touches
10 conflicts
0x92385428…6941
0x34b655…2a6f
10 touches
10 conflicts
0xf9e23360…8ef7
0x34b655…2a6f
10 touches
10 conflicts
0x5f72d58f…c445
0x34b655…2a6f
8 touches
6 conflicts
0x890eac6e…1c0d
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
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
78 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity