← previous blocknext block →recent activity
Analyzing
Block #84,461,434
39 transactions · 31 stateful · 2026-06-29 12:08:21 UTC
Parallelism
85/100
Blocked
61%
Avg conflicts / tx
1.15
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #84,461,434 · 39 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
1w02w13w24w05w17w39w011w112w213w315w416w519w020w127w133w2
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…0002
0xd637b3…4160
12 touches
15 conflicts
0xe99d8e68…a16e
0x34b655…2a6f
10 touches
10 conflicts
0xa68d5e84…0f7c
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…001c
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…002c
0x1b6862…e19c
6 touches
3 conflicts
0x14af78bb…aeda
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x1274880c…3cdc
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: 0xd637b38f…c64160
15 conflicts on slot 0x0000000000…000002
Audit this contract →
← previous block·next block →recent activity