← previous blocknext block →recent activity
Analyzing
Block #85,855,927
10 transactions · 8 stateful · 2026-07-05 23:03:53 UTC
Parallelism
80/100
Blocked
13%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,855,927 · 10 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
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x667658e1…e172
0x34b655…2a6f
4 touches
1 conflict
0xb838bbe6…2931
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x51d41f7a…6397
0x34b655…2a6f
4 touches
1 conflict
0x54a035dd…16c6
0x34b655…2a6f
4 touches
1 conflict
0xd1a0adf6…6e55
0x54cd53…9e7d
2 touches
0 conflicts
0x0b06c320…f278
0x6657d1…8ccc
2 touches
0 conflicts
0x1f277079…e871
0x6657d1…8ccc
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 0x667658e1ed…4de172
Audit this contract →
← previous block·next block →recent activity