← previous blocknext block →recent activity
Analyzing
Block #86,947,370
48 transactions · 41 stateful · 2026-07-11 00:35:57 UTC
Parallelism
58/100
Blocked
71%
Avg conflicts / tx
3.63
Longest chain
20 deep
Execution timeline
did this block parallelize well?
view
block #86,947,370 · 48 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
4w05w16w29w310w411w514w015w116w217w318w419w535w236w637w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
30 touches
105 conflicts
0xb06917e8…6985
0x34b655…2a6f
12 touches
15 conflicts
0x216ffe66…1f94
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
12 touches
15 conflicts
0x8a35acfb…d1ac
0xb1dbf0…c0d3
10 touches
10 conflicts
0xac3e4969…39e9
0x34b655…2a6f
10 touches
10 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xedcf2991…8551
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
105 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity