← previous blocknext block →recent activity
Analyzing
Block #85,928,158
12 transactions · 9 stateful · 2026-07-06 07:04:56 UTC
Parallelism
83/100
Blocked
22%
Avg conflicts / tx
0.17
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,928,158 · 12 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w06w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xbdb569b8…c9e2
0x34b655…2a6f
4 touches
1 conflict
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x1fdeff02…6d28
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0x2832afc3…93c4
0x34b655…2a6f
4 touches
1 conflict
0x9092da13…341b
0x34b655…2a6f
4 touches
1 conflict
0xdd94b8bd…9b2b
0x40c49f…2af0
2 touches
0 conflicts
0xe65d0401…3b0d
0x40c49f…2af0
2 touches
0 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
1 conflict on slot 0xbdb569b887…34c9e2
Audit this contract →
← previous block·next block →recent activity