← previous blocknext block →recent activity
Analyzing
Block #96,694,746
16 transactions · 14 stateful · 2026-08-17 05:39:23 UTC
Parallelism
63/100
Blocked
64%
Avg conflicts / tx
1.56
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,694,746 · 16 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
1w02w13w24w36w07w18w29w310w411w414w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
12 touches
15 conflicts
0x482471ad…122f
0x34b655…2a6f
10 touches
10 conflicts
0x4e169881…8c80
0x34b655…2a6f
10 touches
10 conflicts
0x4c25d47e…29ff
0xd32edf…ff58
9 touches
10 conflicts
0x00000000…0028
0x1b6862…e19c
6 touches
3 conflicts
0xd59f6ed1…03e4
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0012
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity