← previous blocknext block →recent activity
Analyzing
Block #86,059,252
30 transactions · 26 stateful · 2026-07-06 21:40:14 UTC
Parallelism
70/100
Blocked
54%
Avg conflicts / tx
1.17
Longest chain
9 deep
Execution timeline
did this block parallelize well?
view
block #86,059,252 · 30 txs across 9 waves · depth 9
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w36w07w08w115w017w118w419w122w223w324w425w526w627w728w8
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xd98b3c10…67b8
0x34b655…2a6f
14 touches
21 conflicts
0x1aaf4996…65ec
0x34b655…2a6f
8 touches
6 conflicts
0xfaf37ec8…7cdd
0xd32edf…ff58
7 touches
6 conflicts
0xb138d087…4689
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…001c
0x1b6862…e19c
4 touches
1 conflict
0x00000000…002c
0x1b6862…e19c
4 touches
1 conflict
0xd996735f…8732
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
21 conflicts on slot 0xd98b3c102b…ca67b8
Audit this contract →
← previous block·next block →recent activity