← previous blocknext block →recent activity

Analyzing

Block #99,271,514

16 transactions · 15 stateful · 2026-08-26 07:39:28 UTC

Parallelism

69/100

Blocked

47%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,271,514  ·  16 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

0x6ac4a9ce…5f63

0x34b655…2a6f

4 touches
1 conflict

0x9de538e5…7633

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xef234cb9…7713

0x34b655…2a6f

4 touches
1 conflict

0x0b00aeff…7bd3

0x34b655…2a6f

4 touches
1 conflict

0x222e523b…bda2

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