← previous blocknext block →recent activity
Analyzing
Block #96,534,734
15 transactions · 14 stateful · 2026-08-16 16:14:36 UTC
Parallelism
53/100
Blocked
57%
Avg conflicts / tx
1.87
Longest chain
7 deep
Execution timeline
did this block parallelize well?
view
block #96,534,734 · 15 txs across 7 waves · depth 7
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
wave w6
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
2w03w14w25w36w07w28w39w410w512w6
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x482471ad…122f
0x34b655…2a6f
14 touches
21 conflicts
0xc824469a…6425
0x34b655…2a6f
14 touches
21 conflicts
0xbdc80bf7…e947
0x34b655…2a6f
12 touches
15 conflicts
0x3e6302c8…64f5
0x34b655…2a6f
8 touches
6 conflicts
0x53f393fa…00b9
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x1b287091…65ac
0x34b655…2a6f
6 touches
3 conflicts
0xd5c56995…6d21
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
21 conflicts on slot 0x482471adbb…39122f
Audit this contract →
← previous block·next block →recent activity