← previous blocknext block →recent activity
Analyzing
Block #85,511,786
8 transactions · 7 stateful · 2026-07-04 08:50:49 UTC
Parallelism
63/100
Blocked
29%
Avg conflicts / tx
0.25
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #85,511,786 · 8 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
4w06w17w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xcd4227d4…c28d
0x34b655…2a6f
4 touches
1 conflict
0x6637e421…af93
0x34b655…2a6f
4 touches
1 conflict
0xd98b3c10…67b8
0x34b655…2a6f
4 touches
1 conflict
0x89999c15…fdac
0x34b655…2a6f
2 touches
0 conflicts
0xae8b8897…fb17
0x34b655…2a6f
2 touches
0 conflicts
0xc824469a…6425
0x34b655…2a6f
2 touches
0 conflicts
0xcbd788cd…1049
0x34b655…2a6f
2 touches
0 conflicts
0xcd81cc7b…8da0
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 0xcd4227d49b…1bc28d
Audit this contract →
← previous block·next block →recent activity