← previous blocknext block →recent activity
Analyzing
Block #85,813,471
17 transactions · 13 stateful · 2026-07-05 18:21:03 UTC
Parallelism
65/100
Blocked
54%
Avg conflicts / tx
0.82
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #85,813,471 · 17 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w14w05w19w010w113w214w315w416w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x06c59b8c…89c0
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xa62791bc…c2ec
0x34b655…2a6f
6 touches
4 conflicts
0xff98d0f5…46f6
0x34b655…2a6f
6 touches
3 conflicts
0x7e17e82a…9748
0x34b655…2a6f
6 touches
3 conflicts
0xa1571d54…ae41
0x34b655…2a6f
6 touches
3 conflicts
0xaef8650f…25f1
0x34b655…2a6f
6 touches
3 conflicts
0xd99b3b64…1c95
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0x06c59b8c41…2989c0
Audit this contract →
← previous block·next block →recent activity