← previous blocknext block →recent activity

Analyzing

Block #98,663,597

22 transactions · 22 stateful · 2026-08-24 04:28:00 UTC

Parallelism

68/100

Blocked

36%

Avg conflicts / tx

1.05

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #98,663,597  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x7aa91b8f…d070

0x2b46c0…1669

2 touches
0 conflicts

0xb05cd4f5…73d0

0x2b46c0…1669

2 touches
0 conflicts

0xe2263bea…6a9e

0x2b46c0…1669

2 touches
0 conflicts

0xe2263bea…6aa2

0x2b46c0…1669

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)

21 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity