← previous blocknext block →recent activity
Analyzing
Block #96,795,677
49 transactions · 45 stateful · 2026-08-17 14:07:02 UTC
Parallelism
67/100
Blocked
64%
Avg conflicts / tx
2.53
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #96,795,677 · 49 txs across 16 waves · depth 16
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
wave w7
wave w8
wave w9
wave w10
wave w11
wave w12
wave w13
wave w14
wave w15
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
4w05w06w17w28w39w011w113w215w316w417w518w619w724w132w833w935w1037w439w1140w548w15
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
16 touches
28 conflicts
0x03aa8b26…118a
0x34b655…2a6f
14 touches
21 conflicts
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0x988a4b26…82f8
0x34b655…2a6f
10 touches
10 conflicts
0xbcbf5d09…8bac
0x34b655…2a6f
10 touches
10 conflicts
0x6847107a…f468
0xa6afd3…d132
8 touches
6 conflicts
0x889d5e90…929a
0x2a68ba…90c5
8 touches
6 conflicts
0xacd1b162…bee6
0x34b655…2a6f
8 touches
6 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
28 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity