← previous blocknext block →recent activity

Analyzing

Block #99,448,583

19 transactions · 18 stateful · 2026-08-26 22:30:50 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.42

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,448,583  ·  19 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

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xe97d54c5…ef6f

0x34b655…2a6f

4 touches
1 conflict

0xadce6355…03bf

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x078d8bd7…3fff

0x34b655…2a6f

4 touches
1 conflict

0x2202504e…fad0

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35d

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

1 conflict on slot 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity