← previous blocknext block →recent activity
Analyzing
Block #96,708,488
21 transactions · 19 stateful · 2026-08-17 06:48:30 UTC
Parallelism
71/100
Blocked
58%
Avg conflicts / tx
1.14
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,708,488 · 21 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
1w02w13w25w06w07w18w29w112w313w414w516w119w220w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x6c73c136…2ca1
0x34b655…2a6f
10 touches
10 conflicts
0x482471ad…122f
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…6425
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…0019
0x1b6862…e19c
6 touches
3 conflicts
0x00000000…0029
0x1b6862…e19c
6 touches
3 conflicts
0x784d7a94…949c
0x1b6862…e19c
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
6 touches
3 conflicts
0x0672e4a2…8d1f
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
10 conflicts on slot 0x6c73c136a7…402ca1
Audit this contract →
← previous block·next block →recent activity