← previous blocknext block →recent activity
Analyzing
Block #96,599,926
36 transactions · 32 stateful · 2026-08-16 21:42:30 UTC
Parallelism
56/100
Blocked
66%
Avg conflicts / tx
2.75
Longest chain
16 deep
Execution timeline
did this block parallelize well?
view
block #96,599,926 · 36 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
1w02w03w14w05w06w17w28w19w310w211w412w513w614w715w816w917w122w1028w229w334w14
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb3fb9fb5…64db
0x34b655…2a6f
20 touches
45 conflicts
0x2d651956…12e8
0x34b655…2a6f
16 touches
28 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0x840d3ab7…c8c4
0x34b655…2a6f
8 touches
6 conflicts
0xac2a0273…721b
0x34b655…2a6f
8 touches
6 conflicts
0x41bc5f7b…26f2
0x34b655…2a6f
6 touches
3 conflicts
0x79adeae4…34ff
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
45 conflicts on slot 0xb3fb9fb561…7664db
Audit this contract →
← previous block·next block →recent activity