← previous blocknext block →recent activity
Analyzing
Block #86,732,825
62 transactions · 48 stateful · 2026-07-10 00:42:00 UTC
Parallelism
68/100
Blocked
69%
Avg conflicts / tx
3.21
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,732,825 · 62 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
4w05w16w27w39w411w015w117w018w119w220w321w422w523w638w242w343w444w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
24 touches
66 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
18 touches
36 conflicts
0x74888025…a5b8
0x34b655…2a6f
12 touches
15 conflicts
0xac2a0273…721b
0x34b655…2a6f
12 touches
15 conflicts
0x737acb78…fce8
0x34b655…2a6f
12 touches
15 conflicts
0x8eb0ac6b…a73a
0x34b655…2a6f
12 touches
15 conflicts
0x7fdaecd9…d81e
0x34b655…2a6f
10 touches
10 conflicts
0xa1571d54…ae41
0x34b655…2a6f
10 touches
10 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
66 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity