← previous blocknext block →recent activity
Analyzing
Block #85,928,567
22 transactions · 18 stateful · 2026-07-06 07:07:39 UTC
Parallelism
82/100
Blocked
44%
Avg conflicts / tx
0.59
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,928,567 · 22 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
2w03w15w06w17w08w09w110w211w112w013w117w220w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1aaf4996…65ec
0x34b655…2a6f
8 touches
6 conflicts
0xe5bb3628…e5f1
0x34b655…2a6f
6 touches
3 conflicts
0xafd867b7…2b2e
0x34b655…2a6f
6 touches
3 conflicts
0xafd867b7…2b2d
0x34b655…2a6f
6 touches
3 conflicts
0x22e0cc1d…ad04
0x34b655…2a6f
4 touches
1 conflict
0x265d35de…2f86
0x34b655…2a6f
4 touches
1 conflict
0x30323797…a638
0x34b655…2a6f
4 touches
1 conflict
0x49f58aca…82bd
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 0x1aaf499609…4665ec
Audit this contract →
← previous block·next block →recent activity