← previous blocknext block →recent activity
Analyzing
Block #96,613,706
16 transactions · 15 stateful · 2026-08-16 22:51:48 UTC
Parallelism
69/100
Blocked
53%
Avg conflicts / tx
0.88
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,613,706 · 16 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
1w02w13w24w05w36w48w211w212w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xb91ef3ab…19ff
0x34b655…2a6f
6 touches
3 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x2d651956…12e8
0x34b655…2a6f
6 touches
3 conflicts
0xec7d120d…7084
0x34b655…2a6f
6 touches
3 conflicts
0x4acbdbcf…a8c6
0x34b655…2a6f
6 touches
3 conflicts
0xd9f18d9a…141d
0x1b6862…e19c
4 touches
1 conflict
0xf8480e2a…dff5
0x1b6862…e19c
4 touches
1 conflict
0x0c612d13…2829
0x34b655…2a6f
4 touches
1 conflict
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 0xb91ef3ab64…d119ff
Audit this contract →
← previous block·next block →recent activity