← previous blocknext block →recent activity
Analyzing
Block #86,819,966
49 transactions · 42 stateful · 2026-07-10 10:24:06 UTC
Parallelism
73/100
Blocked
74%
Avg conflicts / tx
2.9
Longest chain
13 deep
Execution timeline
did this block parallelize well?
view
block #86,819,966 · 49 txs across 13 waves · depth 13
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
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w06w17w08w19w211w312w416w017w118w219w320w421w522w623w724w825w930w233w240w342w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
26 touches
78 conflicts
0x0f4cddfd…3085
0x34b655…2a6f
20 touches
45 conflicts
0xd1ec0dfd…ccc0
0xc8689a…ee79
16 touches
28 conflicts
0x26249d3e…0f22
0x34b655…2a6f
16 touches
28 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
16 touches
28 conflicts
0x873b97ca…9f25
0x34b655…2a6f
16 touches
28 conflicts
0xb4731b47…b7af
0x34b655…2a6f
16 touches
28 conflicts
0xb7a47e62…7963
0x34b655…2a6f
16 touches
28 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