← previous blocknext block →recent activity
Analyzing
Block #96,708,677
30 transactions · 25 stateful · 2026-08-17 06:49:27 UTC
Parallelism
73/100
Blocked
52%
Avg conflicts / tx
1.1
Longest chain
8 deep
Execution timeline
did this block parallelize well?
view
block #96,708,677 · 30 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
1w02w14w05w26w07w28w310w311w112w217w419w521w623w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1bf8d2af…d140
0x34b655…2a6f
12 touches
15 conflicts
0xd676e291…3ecf
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x98042ee6…66ff
0xd32edf…ff58
7 touches
6 conflicts
0x00000000…0015
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x485d2778…aa5b
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
15 conflicts on slot 0x1bf8d2afa1…d2d140
Audit this contract →
← previous block·next block →recent activity