← previous blocknext block →recent activity
Analyzing
Block #85,767,057
16 transactions · 8 stateful · 2026-07-05 13:11:52 UTC
Parallelism
81/100
Blocked
25%
Avg conflicts / tx
0.13
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,767,057 · 16 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w16w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x22e0cc1d…ad0d
0x34b655…2a6f
4 touches
1 conflict
0xd9a92b6a…01dc
0x34b655…2a6f
4 touches
1 conflict
0x97f73039…aa68
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0x9ff176a9…152e
0x065c9d…c394
2 touches
0 conflicts
0xd0925873…80e6
0x065c9d…c394
2 touches
0 conflicts
0x7d42dc8b…fdb6
0x2a68ba…90c5
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 0xafd867b7ed…d92b2e
Audit this contract →
← previous block·next block →recent activity