← previous blocknext block →recent activity
Analyzing
Block #85,966,273
13 transactions · 11 stateful · 2026-07-06 11:19:15 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.31
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,966,273 · 13 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
6w07w110w111w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c595e56…d5ff
0x34b655…2a6f
4 touches
1 conflict
0x6cda3f80…809b
0x34b655…2a6f
4 touches
1 conflict
0x79b3209b…f766
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f0
0x34b655…2a6f
4 touches
1 conflict
0x9a3068dd…18f1
0x34b655…2a6f
4 touches
1 conflict
0xae2da12e…1a4f
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x0fc41e7b…6831
0x98dc6e…8633
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 0x6c595e5653…44d5ff
Audit this contract →
← previous block·next block →recent activity