← previous blocknext block →recent activity
Analyzing
Block #86,956,806
62 transactions · 47 stateful · 2026-07-11 01:39:00 UTC
Parallelism
71/100
Blocked
79%
Avg conflicts / tx
3.29
Longest chain
18 deep
Execution timeline
did this block parallelize well?
view
block #86,956,806 · 62 txs across 18 waves · depth 18
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w211w312w414w515w516w617w718w828w847w948w1050w1151w1252w12
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0xb06917e8…6985
0x34b655…2a6f
18 touches
36 conflicts
0xd9fb25af…c32b
0xd32edf…ff58
15 touches
28 conflicts
0xf2f76ab3…623e
0x2a68ba…90c5
14 touches
21 conflicts
0xb0a33dea…614c
0x34b655…2a6f
14 touches
21 conflicts
0x7cb2f3fa…4836
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x2484cc15…5afc
0x34b655…2a6f
12 touches
15 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