← previous blocknext block →recent activity

Analyzing

Block #95,197,284

20 transactions · 20 stateful · 2026-08-11 23:52:09 UTC

Parallelism

60/100

Blocked

45%

Avg conflicts / tx

1.75

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,197,284  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xa1087a5c…66c4

0x754704…b603

16 touches
28 conflicts

0x2b54cadb…4425

0xd18b7e…414b

16 touches
28 conflicts

0x3a921be0…779c

0x2a68ba…90c5

10 touches
10 conflicts

0x1f3a75bd…afd6

0x40c49f…2af0

9 touches
10 conflicts

0xebf1d75a…1bd3

0x40c49f…2af0

8 touches
6 conflicts

0x002fed35…79fa

0x2a68ba…90c5

8 touches
6 conflicts

0x595233b5…c4aa

0x754704…b603

4 touches
1 conflict

0x91eb94de…b47b

0x754704…b603

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)

28 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity