← previous blocknext block →recent activity
Analyzing
Block #96,293,427
14 transactions · 13 stateful · 2026-08-15 20:00:38 UTC
Parallelism
71/100
Blocked
23%
Avg conflicts / tx
0.43
Longest chain
4 deep
Execution timeline
did this block parallelize well?
view
block #96,293,427 · 14 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
6w07w110w212w3
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0xc824469a…641f
0x34b655…2a6f
8 touches
6 conflicts
0x00000000…00c9
0x34b655…2a6f
8 touches
6 conflicts
0xc824469a…642d
0x34b655…2a6f
6 touches
3 conflicts
0x2e9d65ac…2265
0x34b655…2a6f
6 touches
3 conflicts
0x56a284d9…32e4
0x34b655…2a6f
6 touches
3 conflicts
0x9a9383a9…6bc7
0x34b655…2a6f
6 touches
3 conflicts
0xa4e9800f…4ab0
0x34b655…2a6f
6 touches
3 conflicts
0xbcab7dbe…2825
0x34b655…2a6f
6 touches
3 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
6 conflicts on slot 0xc824469a90…af641f
Audit this contract →
← previous block·next block →recent activity