← previous blocknext block →recent activity
Analyzing
Block #85,844,762
34 transactions · 24 stateful · 2026-07-05 21:49:24 UTC
Parallelism
85/100
Blocked
33%
Avg conflicts / tx
0.53
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,844,762 · 34 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w05w013w118w219w322w327w028w129w230w331w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
10 touches
10 conflicts
0x7edb5d42…4fad
0xd32edf…ff58
7 touches
6 conflicts
0x070a562a…8147
0x34b655…2a6f
6 touches
3 conflicts
0x080ca4e8…d573
0x34b655…2a6f
6 touches
3 conflicts
0xb4e0a934…5fc7
0x34b655…2a6f
6 touches
3 conflicts
0xea02471d…1542
0x34b655…2a6f
6 touches
3 conflicts
0x85a88798…f85e
0x34b655…2a6f
4 touches
1 conflict
0x6f6b4878…d72d
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
10 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity