← previous blocknext block →recent activity

Analyzing

Block #95,181,465

22 transactions · 22 stateful · 2026-08-11 22:32:35 UTC

Parallelism

55/100

Blocked

55%

Avg conflicts / tx

2.23

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #95,181,465  ·  22 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

20 touches
45 conflicts

0x2b54cadb…4425

0xd18b7e…414b

20 touches
45 conflicts

0xcdc43c63…7e57

0x40c49f…2af0

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0x2e197b62…94b1

0x40c49f…2af0

10 touches
10 conflicts

0x6518075e…2b17

0x2a68ba…90c5

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

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

45 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity