← previous blocknext block →recent activity
Analyzing
Block #86,802,860
13 transactions · 11 stateful · 2026-07-10 08:29:47 UTC
Parallelism
54/100
Blocked
55%
Avg conflicts / tx
0.92
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #86,802,860 · 13 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w04w15w28w39w410w311w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc6ed530e…fa7d
0x34b655…2a6f
8 touches
6 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…6425
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xbba05d16…b776
0x34b655…2a6f
6 touches
3 conflicts
0x9e599b87…c270
0x34b655…2a6f
4 touches
1 conflict
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
6 conflicts on slot 0xc6ed530ecc…a9fa7d
Audit this contract →
← previous block·next block →recent activity