← previous blocknext block →recent activity

Analyzing

Block #95,474,710

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

Parallelism

73/100

Blocked

42%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #95,474,710  ·  22 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

0x11b69a7e…334e

0xee8c0e…1242

10 touches
10 conflicts

0xbb1d4922…ec5f

0xa6afd3…d132

8 touches
6 conflicts

0x2a9e9bd1…5368

0x2a68ba…90c5

8 touches
6 conflicts

0x00000000…0018

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0028

0x1b6862…e19c

4 touches
1 conflict

0x93afca4c…b478

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

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