← previous blocknext block →recent activity

Analyzing

Block #99,284,409

18 transactions · 18 stateful · 2026-08-26 08:44:20 UTC

Parallelism

72/100

Blocked

44%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,284,409  ·  18 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x3c78ca04…432c

0x34b655…2a6f

4 touches
1 conflict

0x3e6302c8…64f5

0x34b655…2a6f

4 touches
1 conflict

0x41469894…598f

0x34b655…2a6f

4 touches
1 conflict

0x41469894…5990

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x49890ced…6f23

0x34b655…2a6f

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)

10 conflicts on slot 0xd17580f913…78ece1

← previous block·next block →recent activity