← previous blocknext block →recent activity

Analyzing

Block #99,080,903

21 transactions · 18 stateful · 2026-08-25 15:40:08 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,080,903  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xfcd5e68f…2a12

0x34b655…2a6f

6 touches
3 conflicts

0xf450262f…fdd5

0xd32edf…ff58

5 touches
3 conflicts

0x45b67460…28a5

0x1b6862…e19c

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xa0632a87…9d5b

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x41755291…977f

0x065c9d…c394

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: Perpl

3 conflicts on slot 0xfcd5e68f28…382a12

← previous block·next block →recent activity