← previous blocknext block →recent activity
Analyzing
Block #85,819,207
16 transactions · 13 stateful · 2026-07-05 18:59:11 UTC
Parallelism
75/100
Blocked
46%
Avg conflicts / tx
0.44
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,819,207 · 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
1w02w04w05w16w17w112w213w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xda2ee2e7…968a
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
4 touches
1 conflict
0x039a9955…6771
0x34b655…2a6f
4 touches
1 conflict
0x1d720942…075a
0x34b655…2a6f
4 touches
1 conflict
0x3151b440…d0aa
0x34b655…2a6f
4 touches
1 conflict
0x3e505a15…70f8
0x34b655…2a6f
4 touches
1 conflict
0x71de3d02…899d
0x34b655…2a6f
4 touches
1 conflict
0x72470f81…c402
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 0xda2ee2e777…e7968a
Audit this contract →
← previous block·next block →recent activity