← previous blocknext block →recent activity
Analyzing
Block #86,962,750
50 transactions · 41 stateful · 2026-07-11 02:18:44 UTC
Parallelism
66/100
Blocked
66%
Avg conflicts / tx
2.24
Longest chain
17 deep
Execution timeline
did this block parallelize well?
view
block #86,962,750 · 50 txs across 17 waves · depth 17
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w110w216w017w118w219w320w421w522w623w724w825w926w1032w233w136w338w439w540w543w1244w13
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
22 touches
55 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0xb06917e8…6985
0x34b655…2a6f
10 touches
10 conflicts
0x8a35acfb…d1aa
0xb1dbf0…c0d3
10 touches
10 conflicts
0x00000000…003d
0xa6afd3…d132
10 touches
10 conflicts
0xb6ed530c…d450
0x34b655…2a6f
8 touches
6 conflicts
0x1941b441…5889
0x34b655…2a6f
8 touches
6 conflicts
0xc7a15219…7745
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
55 conflicts on slot 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity