← previous blocknext block →recent activity

Analyzing

Block #95,425,484

23 transactions · 21 stateful · 2026-08-12 19:13:31 UTC

Parallelism

74/100

Blocked

48%

Avg conflicts / tx

1.3

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,425,484  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x991bdb19…acc5

0xd32edf…ff58

11 touches
15 conflicts

0x2b54cadb…4425

0xd18b7e…414b

10 touches
10 conflicts

0x6e3a6d5c…1c45

0x40c49f…2af0

8 touches
6 conflicts

0x6518075e…2b17

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x6aa624fd…a852

0x1b6862…e19c

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)

15 conflicts on slot 0xa1087a5ca6…0a66c4

← previous block·next block →recent activity