← previous blocknext block →recent activity
Analyzing
Block #94,796,253
20 transactions · 20 stateful · 2026-08-10 14:14:09 UTC
Parallelism
70/100
Blocked
45%
Avg conflicts / tx
1
Longest chain
6 deep
Execution timeline
did this block parallelize well?
view
block #94,796,253 · 20 txs across 6 waves · depth 6
parallel ↔ serial
wave w0
wave w1
wave w2
wave w3
wave w4
wave w5
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
1w02w13w04w25w07w18w010w111w212w313w415w418w5
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x00000000…00c9
0x34b655…2a6f
10 touches
10 conflicts
0xca841faa…486a
0x34b655…2a6f
8 touches
6 conflicts
0xc2b37cdc…e470
0x34b655…2a6f
6 touches
3 conflicts
0xc824469a…641f
0x34b655…2a6f
6 touches
3 conflicts
0x7210391a…8b8f
0x34b655…2a6f
6 touches
3 conflicts
0x0caf137e…a770
0x34b655…2a6f
6 touches
3 conflicts
0x4e51a63d…2b55
0x34b655…2a6f
6 touches
3 conflicts
0x695ff42b…6946
0xd32edf…ff58
5 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
10 conflicts on slot 0x0000000000…0000c9
Audit this contract →
← previous block·next block →recent activity