← previous blocknext block →recent activity
Analyzing
Block #85,166,422
14 transactions · 13 stateful · 2026-07-02 18:30:50 UTC
Parallelism
79/100
Blocked
23%
Avg conflicts / tx
0.36
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,166,422 · 14 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
1w05w06w18w19w013w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x74888025…a5b8
0x34b655…2a6f
6 touches
3 conflicts
0x922c7ebd…6600
0xc8689a…ee79
4 touches
1 conflict
0xe47478a3…a058
0x34b655…2a6f
4 touches
1 conflict
0xe4fd416a…b2e4
0x34b655…2a6f
4 touches
1 conflict
0xe93b0dc1…d5f5
0x34b655…2a6f
4 touches
1 conflict
0xed660153…a905
0x34b655…2a6f
4 touches
1 conflict
0xfaef08b1…0696
0x34b655…2a6f
4 touches
1 conflict
0x00000000…003d
0x40c49f…2af0
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 0x74888025b0…84a5b8
Audit this contract →
← previous block·next block →recent activity