← previous blocknext block →recent activity

Analyzing

Block #100,030,806

17 transactions · 17 stateful · 2026-08-28 23:35:27 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,030,806  ·  17 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

0xffaa25f5…1528

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2592

0x34b655…2a6f

6 touches
3 conflicts

0x8649d60a…16f6

0x34b655…2a6f

6 touches
3 conflicts

0x9ca6fa7b…aeb3

0x34b655…2a6f

6 touches
3 conflicts

0xa169711f…c7f3

0x34b655…2a6f

6 touches
3 conflicts

0xd2a76d80…ee44

0x34b655…2a6f

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

6 conflicts on slot 0xffaa25f553…241528

← previous block·next block →recent activity