← previous blocknext block →recent activity
Analyzing
Block #85,576,622
21 transactions · 18 stateful · 2026-07-04 16:02:36 UTC
Parallelism
71/100
Blocked
39%
Avg conflicts / tx
0.38
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,576,622 · 21 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w17w08w110w211w312w119w420w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x56153262…21ce
0x34b655…2a6f
6 touches
3 conflicts
0x13a54fa2…5ae3
0x2a68ba…90c5
4 touches
1 conflict
0x05edf2cf…ac3c
0x34b655…2a6f
4 touches
1 conflict
0x0f6aef87…8137
0x34b655…2a6f
4 touches
1 conflict
0x663d3288…f460
0x34b655…2a6f
4 touches
1 conflict
0x8cecf700…ee94
0x34b655…2a6f
4 touches
1 conflict
0x8e63f306…205a
0x34b655…2a6f
4 touches
1 conflict
0x9b2c9ea3…e825
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 0x5615326245…a221ce
Audit this contract →
← previous block·next block →recent activity