← previous blocknext block →recent activity
Analyzing
Block #86,738,099
16 transactions · 13 stateful · 2026-07-10 01:17:14 UTC
Parallelism
75/100
Blocked
38%
Avg conflicts / tx
0.5
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #86,738,099 · 16 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
2w05w06w17w08w111w112w213w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0x1bde87f2…0843
0x34b655…2a6f
4 touches
1 conflict
0x248e43aa…7287
0x34b655…2a6f
4 touches
1 conflict
0x56b5f5c0…a3ad
0x34b655…2a6f
4 touches
1 conflict
0x72ee2f48…0929
0x34b655…2a6f
4 touches
1 conflict
0x737acb78…fce8
0x34b655…2a6f
4 touches
1 conflict
0x79287e09…898a
0x34b655…2a6f
4 touches
1 conflict
0x816c7d6d…98ea
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
3 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity