← previous blocknext block →recent activity
Analyzing
Block #86,979,353
39 transactions · 35 stateful · 2026-07-11 04:09:37 UTC
Parallelism
80/100
Blocked
60%
Avg conflicts / tx
1.33
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #86,979,353 · 39 txs across 8 waves · depth 8
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w15w26w38w313w216w017w318w019w120w221w322w423w332w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb6ed530c…d450
0x34b655…2a6f
10 touches
10 conflicts
0x00000000…0002
0x04fdea…47d7
10 touches
10 conflicts
0xdd70bea3…1ffe
0x3bd359…433a
8 touches
6 conflicts
0xea02471d…1542
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0xf52bfe7e…bfd2
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
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
10 conflicts on slot 0xb6ed530c56…eed450
Audit this contract →
← previous block·next block →recent activity