← previous blocknext block →recent activity

Analyzing

Block #97,529,065

20 transactions · 18 stateful · 2026-08-20 04:21:23 UTC

Parallelism

60/100

Blocked

50%

Avg conflicts / tx

1.25

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #97,529,065  ·  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

12 touches
15 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0xea21cf6a…1e68

0x065c9d…c394

9 touches
10 conflicts

0x0778475b…bd75

0x2a68ba…90c5

6 touches
3 conflicts

0xbd6329be…a3d5

0xd32edf…ff58

5 touches
3 conflicts

0x00000000…0019

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0029

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