← previous blocknext block →recent activity

Analyzing

Block #95,480,407

15 transactions · 13 stateful · 2026-08-12 23:49:48 UTC

Parallelism

87/100

Blocked

23%

Avg conflicts / tx

0.2

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #95,480,407  ·  15 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

- write/write- - read/write

x = tx position · y = wave (depth)

Hot storage slots

Contention

0xa949d556…184c

0x754704…b603

4 touches
1 conflict

0xaad1c5c0…ab91

0x754704…b603

4 touches
1 conflict

0xdc255d21…c377

0x754704…b603

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eeb

0x34b655…2a6f

4 touches
1 conflict

0x9b2d3bee…8eec

0x34b655…2a6f

4 touches
1 conflict

0x4dbb0f3e…2028

0x99c7a7…8bf0

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: USDC (USDC)

1 conflict on slot 0xa949d556b1…83184c

← previous block·next block →recent activity