← previous blocknext block →recent activity

Analyzing

Block #95,298,732

16 transactions · 16 stateful · 2026-08-12 08:31:42 UTC

Parallelism

81/100

Blocked

13%

Avg conflicts / tx

0.19

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,298,732  ·  16 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

parallel · wave 0, no conflictsdelayed · forced to waitconflict source · blocks others

Conflict graph

Blocked by

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0x5311f864…0984

0x754704…b603

6 touches
3 conflicts

0x4bff1030…4580

0x928dc8…8207

3 touches
1 conflict

0x4bff1030…457b

0x928dc8…8207

3 touches
1 conflict

0x4bff1030…457e

0x928dc8…8207

3 touches
1 conflict

0x5b571ba0…f13a

0x368ee5…7ca4

2 touches
0 conflicts

0x68faa0b9…14af

0x368ee5…7ca4

2 touches
0 conflicts

0xcd621226…2df8

0x368ee5…7ca4

2 touches
0 conflicts

0x025e2a02…2ef8

0x754704…b603

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)

3 conflicts on slot 0x5311f86450…380984

← previous block·next block →recent activity