← previous blocknext block →recent activity
Analyzing
Block #86,947,207
35 transactions · 32 stateful · 2026-07-11 00:34:51 UTC
Parallelism
57/100
Blocked
75%
Avg conflicts / tx
2.29
Longest chain
15 deep
Execution timeline
did this block parallelize well?
view
block #86,947,207 · 35 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
1w03w04w15w26w38w09w110w111w012w113w214w315w416w517w618w719w822w123w225w10
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
18 touches
36 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
12 touches
15 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
8 touches
6 conflicts
0x7babfe9a…ff96
0x34b655…2a6f
8 touches
6 conflicts
0xb06917e8…6985
0x34b655…2a6f
8 touches
6 conflicts
0xb0bc3bf8…e2b1
0x34b655…2a6f
8 touches
6 conflicts
0x8a35acfb…d1ad
0xb1dbf0…c0d3
8 touches
6 conflicts
0x8a35acfb…d1ae
0xb1dbf0…c0d3
7 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
36 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity