← previous blocknext block →recent activity
Analyzing
Block #96,601,439
13 transactions · 11 stateful · 2026-08-16 21:50:06 UTC
Parallelism
77/100
Blocked
27%
Avg conflicts / tx
0.54
Longest chain
3 deep
Execution timeline
did this block parallelize well?
view
block #96,601,439 · 13 txs across 3 waves · depth 3
parallel ↔ serial
wave w0
wave w1
wave w2
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w03w16w07w28w011w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x36fb462c…1435
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xc8d59e0f…cfe0
0x34b655…2a6f
6 touches
3 conflicts
0x690c87ea…f239
0x34b655…2a6f
6 touches
3 conflicts
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x5d0a3cbd…ab19
0x34b655…2a6f
4 touches
1 conflict
0x6f132c01…cdcc
0x34b655…2a6f
4 touches
1 conflict
0x80398c66…f3cc
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 0x36fb462c30…fe1435
Audit this contract →
← previous block·next block →recent activity