← previous blocknext block →recent activity
Analyzing
Block #85,105,569
24 transactions · 13 stateful · 2026-07-02 11:44:46 UTC
Parallelism
88/100
Blocked
31%
Avg conflicts / tx
0.21
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,105,569 · 24 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
2w03w14w29w121w022w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xfaef08b1…0696
0x34b655…2a6f
6 touches
3 conflicts
0x2e90d1ef…f110
0x34b655…2a6f
4 touches
1 conflict
0x48b252fc…b818
0x34b655…2a6f
4 touches
1 conflict
0x5ec64628…72e4
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
4 touches
1 conflict
0x6c2aa5be…d808
0x34b655…2a6f
4 touches
1 conflict
0x74f6dacb…1b95
0x34b655…2a6f
4 touches
1 conflict
0x8c982108…7c83
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 0xfaef08b108…f90696
Audit this contract →
← previous block·next block →recent activity