← previous blocknext block →recent activity
Analyzing
Block #85,921,570
12 transactions · 8 stateful · 2026-07-06 06:21:04 UTC
Parallelism
67/100
Blocked
38%
Avg conflicts / tx
0.58
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #85,921,570 · 12 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
2w03w04w15w27w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xafd867b7…2b2e
0x34b655…2a6f
8 touches
6 conflicts
0xafd867b7…2b2d
0x34b655…2a6f
8 touches
6 conflicts
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xee21ba9f…e691
0x34b655…2a6f
5 touches
3 conflicts
0xc0c4d8ad…1185
0x34b655…2a6f
5 touches
3 conflicts
0x67fc285e…2584
0x34b655…2a6f
4 touches
2 conflicts
0x664bf99e…0a8c
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
6 conflicts on slot 0xafd867b7ed…d92b2e
Audit this contract →
← previous block·next block →recent activity