← previous blocknext block →recent activity
Analyzing
Block #96,592,203
15 transactions · 15 stateful · 2026-08-16 21:03:39 UTC
Parallelism
73/100
Blocked
47%
Avg conflicts / tx
0.87
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,592,203 · 15 txs across 4 waves · depth 4
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w25w07w38w19w213w314w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0x60e1f0d3…1e98
0xd32edf…ff58
7 touches
6 conflicts
0xa35509fa…5cb3
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0xfd0fd313…3c8b
0x34b655…2a6f
6 touches
3 conflicts
0xbec23443…9293
0x34b655…2a6f
6 touches
3 conflicts
0x7b41d5cd…00e6
0x34b655…2a6f
5 touches
3 conflicts
0x00000000…001e
0x1b6862…e19c
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
6 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity