← previous blocknext block →recent activity
Analyzing
Block #96,287,401
11 transactions · 9 stateful · 2026-08-15 19:30:20 UTC
Parallelism
55/100
Blocked
44%
Avg conflicts / tx
0.73
Longest chain
5 deep
Execution timeline
did this block parallelize well?
view
block #96,287,401 · 11 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
1w03w04w17w28w39w4
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
6 touches
3 conflicts
0x482471ad…122f
0x34b655…2a6f
6 touches
3 conflicts
0xef5959a3…2a2f
0x34b655…2a6f
4 touches
1 conflict
0xc8d59e0f…cfe0
0x34b655…2a6f
4 touches
1 conflict
0xcec993c9…34bf
0x34b655…2a6f
4 touches
1 conflict
0xe429c946…da29
0x34b655…2a6f
4 touches
1 conflict
0xe429c946…da2a
0x34b655…2a6f
4 touches
1 conflict
0x0db691ab…3ee3
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 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity