← previous blocknext block →recent activity
Analyzing
Block #96,604,259
10 transactions · 9 stateful · 2026-08-16 22:04:17 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.2
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #96,604,259 · 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
1w02w03w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x3226e3fe…f799
0x34b655…2a6f
4 touches
1 conflict
0x4acbdbcf…a8c6
0x34b655…2a6f
4 touches
1 conflict
0x172a2ebf…3c1c
0x34b655…2a6f
2 touches
0 conflicts
0x1e4ffaec…3966
0x34b655…2a6f
2 touches
0 conflicts
0x5b0ed476…61a6
0x34b655…2a6f
2 touches
0 conflicts
0x5f8db915…4cd5
0x34b655…2a6f
2 touches
0 conflicts
0x7de57974…f5ba
0x34b655…2a6f
2 touches
0 conflicts
0x821cf832…19c6
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 0x3226e3fe33…f1f799
Audit this contract →
← previous block·next block →recent activity