← previous blocknext block →recent activity

Analyzing

Block #97,853,895

22 transactions · 19 stateful · 2026-08-21 07:52:22 UTC

Parallelism

82/100

Blocked

32%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,853,895  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd17580f9…ece1

0x754704…b603

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x348fda08…7e96

0x065c9d…c394

4 touches
1 conflict

0x1b60b708…5b4b

0x2b46c0…1669

2 touches
0 conflicts

0x1a7d0dc9…a6ab

0x34b655…2a6f

2 touches
0 conflicts

0x1c268526…53c1

0x34b655…2a6f

2 touches
0 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)

6 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity