← previous blocknext block →recent activity

Analyzing

Block #97,500,013

24 transactions · 23 stateful · 2026-08-20 01:55:13 UTC

Parallelism

67/100

Blocked

65%

Avg conflicts / tx

2.13

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #97,500,013  ·  24 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

0xd17580f9…ece1

0x754704…b603

14 touches
21 conflicts

0x2e307641…c7dc

0x065c9d…c394

10 touches
10 conflicts

0x002fed35…79fa

0x2a68ba…90c5

10 touches
10 conflicts

0xa9ec0f31…177d

0x065c9d…c394

6 touches
3 conflicts

0x0778475b…bd75

0x2a68ba…90c5

6 touches
3 conflicts

0xd65c32c5…3418

0x34b655…2a6f

4 touches
1 conflict

0xda8d6085…7b09

0x34b655…2a6f

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