← previous blocknext block →recent activity
Analyzing
Block #85,171,747
29 transactions · 24 stateful · 2026-07-02 19:06:15 UTC
Parallelism
83/100
Blocked
29%
Avg conflicts / tx
0.34
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,171,747 · 29 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
4w05w112w013w119w221w324w225w326w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x112c35bc…2afc
0x34b655…2a6f
6 touches
3 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
6 touches
3 conflicts
0xcdc1731c…b91a
0x34b655…2a6f
6 touches
3 conflicts
0x1f9ec1ad…d05c
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002a
0x1b6862…e19c
4 touches
1 conflict
0xd9f18d9a…141d
0x1b6862…e19c
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 0x112c35bcb6…972afc
Audit this contract →
← previous block·next block →recent activity