← previous blocknext block →recent activity
Analyzing
Block #86,802,813
18 transactions · 17 stateful · 2026-07-10 08:29:29 UTC
Parallelism
78/100
Blocked
24%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,802,813 · 18 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
8w09w110w111w215w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x8060f612…9559
0x34b655…2a6f
8 touches
6 conflicts
0x7e5ea60a…c4aa
0x34b655…2a6f
6 touches
3 conflicts
0x92385428…6941
0x34b655…2a6f
6 touches
3 conflicts
0xcaf5a5ac…09f0
0x34b655…2a6f
6 touches
3 conflicts
0x38b61269…48d7
0x34b655…2a6f
4 touches
1 conflict
0x482471ad…122f
0x34b655…2a6f
4 touches
1 conflict
0x62030a81…91be
0x34b655…2a6f
4 touches
1 conflict
0x650e90b3…213c
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 0x8060f612b1…089559
Audit this contract →
← previous block·next block →recent activity