← previous blocknext block →recent activity
Analyzing
Block #95,759,242
10 transactions · 9 stateful · 2026-08-13 23:13:18 UTC
Parallelism
80/100
Blocked
11%
Avg conflicts / tx
0.1
Longest chain
2 deep
Execution timeline
did this block parallelize well?
view
block #95,759,242 · 10 txs across 2 waves · depth 2
parallel ↔ serial
wave w0
wave w1
parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others
Conflict graph
Blocked by
6w07w1
- write/write- - read/write
x = tx position · y = wave (depth)
Hot storage slots
Contention
0x1862f4d0…5d68
0x754704…b603
4 touches
1 conflict
0xd17580f9…ece1
0x754704…b603
4 touches
1 conflict
0x1c912a68…3b21
0x2a68ba…90c5
2 touches
0 conflicts
0x1ea0a6bc…6a74
0x2a68ba…90c5
2 touches
0 conflicts
0x3dae5ee1…721b
0x34b655…2a6f
2 touches
0 conflicts
0x414961e3…707e
0x34b655…2a6f
2 touches
0 conflicts
0x628359b1…7263
0x34b655…2a6f
2 touches
0 conflicts
0x72e5a1fc…54ff
0x34b655…2a6f
2 touches
0 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: USDC (USDC)
1 conflict on slot 0x1862f4d053…105d68
Audit this contract →
← previous block·next block →recent activity