← previous blocknext block →recent activity

Analyzing

Block #99,263,598

18 transactions · 17 stateful · 2026-08-26 06:59:39 UTC

Parallelism

56/100

Blocked

59%

Avg conflicts / tx

1.72

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,263,598  ·  18 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

0xd17580f9…ece1

0x754704…b603

16 touches
28 conflicts

0x5c455afd…ce06

0x34b655…2a6f

4 touches
1 conflict

0x883b1ea6…2acf

0x34b655…2a6f

4 touches
1 conflict

0x9a5dfcea…f513

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x00000000…001c

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002c

0x1b6862…e19c

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)

28 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity