← previous blocknext block →recent activity

Analyzing

Block #99,278,454

18 transactions · 18 stateful · 2026-08-26 08:14:22 UTC

Parallelism

61/100

Blocked

44%

Avg conflicts / tx

1.28

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #99,278,454  ·  18 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

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xfb8cab34…dd97

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

0x34b655…2a6f

4 touches
1 conflict

0x2c31d778…773e

0x34b655…2a6f

2 touches
0 conflicts

0x47ee9f76…8dee

0x34b655…2a6f

2 touches
0 conflicts

0x47ee9f76…8def

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)

21 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity