← previous blocknext block →recent activity
Analyzing
Block #96,286,630
10 transactions · 9 stateful · 2026-08-15 19:26:27 UTC
Parallelism
80/100
Blocked
22%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,286,630 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
3w04w07w18w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x0df5574e…d4db
0x34b655…2a6f
4 touches
1 conflict
0x236533a6…52ac
0x34b655…2a6f
4 touches
1 conflict
0xa67102b1…9837
0x34b655…2a6f
4 touches
1 conflict
0x6d1b72ee…6b77
0x34b655…2a6f
4 touches
1 conflict
0x33e21d4a…f776
0x34b655…2a6f
3 touches
1 conflict
0x4bc1b6fd…ce27
0x34b655…2a6f
2 touches
0 conflicts
0x6d1b72ee…6b78
0x34b655…2a6f
2 touches
0 conflicts
0x737acb78…fce8
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
1 conflict on slot 0x0df5574ee3…65d4db
Audit this contract →
← previous block·next block →recent activity