← previous blocknext block →recent activity

Analyzing

Block #99,256,566

21 transactions · 21 stateful · 2026-08-26 06:24:11 UTC

Parallelism

62/100

Blocked

48%

Avg conflicts / tx

1.62

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,256,566  ·  21 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

0x631b4113…baa9

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x10f0a1bf…12c3

0x34b655…2a6f

2 touches
0 conflicts

0x1eb0fab5…3517

0x34b655…2a6f

2 touches
0 conflicts

0x25f0fcba…ca8b

0x34b655…2a6f

2 touches
0 conflicts

0x3347cbe5…846c

0x34b655…2a6f

2 touches
0 conflicts

0xa4e03780…74b0

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)

28 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity