← previous blocknext block →recent activity
Analyzing
Block #96,695,561
13 transactions · 11 stateful · 2026-08-17 05:43:29 UTC
Parallelism
54/100
Blocked
45%
Avg conflicts / tx
0.46
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,695,561 · 13 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
3w04w17w28w39w412w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x737acb78…fce8
0x34b655…2a6f
6 touches
3 conflicts
0xac2a0273…721b
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
4 touches
1 conflict
0xe9452241…95a3
0x34b655…2a6f
4 touches
1 conflict
0xebd7c71b…8905
0x34b655…2a6f
4 touches
1 conflict
0x206f4379…e08a
0x34b655…2a6f
4 touches
1 conflict
0x620b761c…270e
0x34b655…2a6f
4 touches
1 conflict
0x6bdb9869…7558
0x34b655…2a6f
2 touches
0 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
3 conflicts on slot 0x737acb7813…fafce8
Audit this contract →
← previous block·next block →recent activity