← previous blocknext block →recent activity
Analyzing
Block #96,611,289
28 transactions · 28 stateful · 2026-08-16 22:39:39 UTC
Parallelism
64/100
Blocked
61%
Avg conflicts / tx
1.29
Longest chain
10 deep
Execution timeline
did this block parallelize well?
view
block #96,611,289 · 28 txs across 10 waves · depth 10
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w27w28w39w311w412w514w615w716w818w119w926w7
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…003d
0xa6afd3…d132
8 touches
6 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
8 touches
6 conflicts
0xa558e115…fc88
0x34b655…2a6f
8 touches
6 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
8 touches
6 conflicts
0x0a6cb118…4caa
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x04717fc0…1cf7
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: Perpl
6 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity