← previous blocknext block →recent activity
Analyzing
Block #85,189,852
13 transactions · 12 stateful · 2026-07-02 21:06:52 UTC
Parallelism
85/100
Blocked
8%
Avg conflicts / tx
0.08
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,189,852 · 13 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
4w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x9a36c85b…96a5
0x34b655…2a6f
4 touches
1 conflict
0xb44564d6…bb43
0x34b655…2a6f
4 touches
1 conflict
0xd63e616b…a07d
0x34b655…2a6f
4 touches
1 conflict
0x06f0d2ab…dd75
0x34b655…2a6f
4 touches
1 conflict
0x1fbae59b…c10f
0x065c9d…c394
2 touches
0 conflicts
0x4aef0e65…c786
0x065c9d…c394
2 touches
0 conflicts
0x4c9e0fe5…8da0
0x065c9d…c394
2 touches
0 conflicts
0x731e6d82…2883
0x065c9d…c394
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 0x9a36c85bd5…bc96a5
Audit this contract →
← previous block·next block →recent activity