← previous blocknext block →recent activity
Analyzing
Block #85,897,129
16 transactions · 11 stateful · 2026-07-06 03:38:14 UTC
Parallelism
88/100
Blocked
9%
Avg conflicts / tx
0.06
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,897,129 · 16 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
0xafd867b7…2b2d
0x34b655…2a6f
4 touches
1 conflict
0xafd867b7…2b2e
0x34b655…2a6f
4 touches
1 conflict
0x1b9ef35b…48bb
0x34b655…2a6f
3 touches
1 conflict
0x568b02ef…f83a
0x34b655…2a6f
3 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
2 touches
0 conflicts
0x14a58ff4…3b6b
0x40c49f…2af0
2 touches
0 conflicts
0x1c1b5eba…66c6
0x40c49f…2af0
2 touches
0 conflicts
0x26aea159…43ab
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 0xafd867b7ed…d92b2d
Audit this contract →
← previous block·next block →recent activity