← previous blocknext block →recent activity
Analyzing
Block #96,369,015
23 transactions · 21 stateful · 2026-08-16 02:20:49 UTC
Parallelism
78/100
Blocked
57%
Avg conflicts / tx
1.26
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,369,015 · 23 txs across 5 waves · depth 5
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w24w37w08w19w010w112w213w314w418w119w221w322w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…6425
0x34b655…2a6f
10 touches
10 conflicts
0x0bd95eb4…e562
0x34b655…2a6f
10 touches
10 conflicts
0xea1b8c07…b969
0x34b655…2a6f
8 touches
6 conflicts
0xd98b3c10…67b8
0x34b655…2a6f
8 touches
6 conflicts
0x424934c8…f2f1
0x34b655…2a6f
8 touches
6 conflicts
0x16f2b4e1…e98b
0x34b655…2a6f
8 touches
6 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x353a3a00…5e0a
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 0xc824469a90…af6425
Audit this contract →
← previous block·next block →recent activity