← previous blocknext block →recent activity

Analyzing

Block #99,263,391

22 transactions · 20 stateful · 2026-08-26 06:58:36 UTC

Parallelism

64/100

Blocked

45%

Avg conflicts / tx

1.41

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,263,391  ·  22 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

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x0b000000…0002

0x000000…1000

2 touches
0 conflicts

0x3a921be0…779c

0x2a68ba…90c5

2 touches
0 conflicts

0x213ee207…a151

0x2b46c0…1669

2 touches
0 conflicts

0x2f74f175…9284

0x2b46c0…1669

2 touches
0 conflicts

0x2f74f175…9285

0x2b46c0…1669

2 touches
0 conflicts

0x2f74f175…9286

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)

28 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity