← previous blocknext block →recent activity
Analyzing
Block #85,995,399
29 transactions · 23 stateful · 2026-07-06 14:33:52 UTC
Parallelism
83/100
Blocked
52%
Avg conflicts / tx
0.69
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #85,995,399 · 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
1w02w13w24w05w16w07w19w012w013w114w215w316w124w125w226w327w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xdba422af…42ec
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0x40c49f…2af0
6 touches
3 conflicts
0xffa7d0a4…b10a
0x40c49f…2af0
6 touches
3 conflicts
0xa28e51d7…a35e
0xd32edf…ff58
5 touches
3 conflicts
0x00000000…0013
0x1b6862…e19c
4 touches
1 conflict
0x00000000…0015
0x1b6862…e19c
4 touches
1 conflict
0x00000000…001a
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
6 conflicts on slot 0xdba422aff7…3642ec
Audit this contract →
← previous block·next block →recent activity