← previous blocknext block →recent activity
Analyzing
Block #85,158,898
13 transactions · 11 stateful · 2026-07-02 17:40:50 UTC
Parallelism
85/100
Blocked
27%
Avg conflicts / tx
0.23
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #85,158,898 · 13 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w06w19w010w111w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc08384da…ecb7
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0xfa2527aa…9dd5
0x34b655…2a6f
4 touches
1 conflict
0x0d748d21…eede
0x34b655…2a6f
2 touches
0 conflicts
0x0ebf1be1…1294
0x34b655…2a6f
2 touches
0 conflicts
0x181732de…9796
0x34b655…2a6f
2 touches
0 conflicts
0x22e0cc1d…ad0d
0x34b655…2a6f
2 touches
0 conflicts
0x40b5f387…a164
0x34b655…2a6f
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 0xc08384da3a…ebecb7
Audit this contract →
← previous block·next block →recent activity