← previous blocknext block →recent activity

Analyzing

Block #99,481,167

19 transactions · 19 stateful · 2026-08-27 01:14:55 UTC

Parallelism

58/100

Blocked

63%

Avg conflicts / tx

1.37

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,481,167  ·  19 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

0xd9722304…6ed0

0x34b655…2a6f

12 touches
15 conflicts

0x89a60368…e532

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0018

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0028

0x1b6862…e19c

6 touches
3 conflicts

0x17a7f697…dcb1

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 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: Perpl

15 conflicts on slot 0xd97223041d…366ed0

← previous block·next block →recent activity