← previous blocknext block →recent activity
Analyzing
Block #96,365,916
20 transactions · 20 stateful · 2026-08-16 02:05:13 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
1.05
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #96,365,916 · 20 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
2w03w16w07w18w29w010w311w412w413w517w519w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x53f393fa…00b9
0x34b655…2a6f
12 touches
15 conflicts
0xca841faa…486a
0x34b655…2a6f
6 touches
3 conflicts
0x18cf36a6…a3a3
0x34b655…2a6f
6 touches
3 conflicts
0xf18c12c4…3e7d
0x34b655…2a6f
4 touches
1 conflict
0x889d5e90…929a
0x2a68ba…90c5
4 touches
1 conflict
0xcdd32c46…e107
0x34b655…2a6f
4 touches
1 conflict
0x4c188934…158e
0x34b655…2a6f
4 touches
1 conflict
0xe6df4062…2966
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
15 conflicts on slot 0x53f393fafd…2a00b9
Audit this contract →
← previous block·next block →recent activity