← previous blocknext block →recent activity

Analyzing

Block #99,290,248

20 transactions · 20 stateful · 2026-08-26 09:13:42 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,290,248  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x85c42e7e…1a12

0x77d53b…8080

6 touches
3 conflicts

0x7e32f1e0…5612

0x77d53b…8080

6 touches
3 conflicts

0x0fd2cbc5…476b

0x77d53b…8080

6 touches
3 conflicts

0xe3abe489…ebf3

0x77d53b…8080

6 touches
3 conflicts

0xd59f6ed1…03e8

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x29104487…7b42

0x77d53b…8080

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)

15 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity