← previous blocknext block →recent activity

Analyzing

Block #100,619,352

35 transactions · 32 stateful · 2026-08-31 01:01:02 UTC

Parallelism

77/100

Blocked

44%

Avg conflicts / tx

1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #100,619,352  ·  35 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

0x90bbbced…dac6

0x34b655…2a6f

10 touches
10 conflicts

0xfd7f5b55…4994

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x15698ac9…2a46

0x34b655…2a6f

6 touches
3 conflicts

0x5086c64a…28ba

0x34b655…2a6f

6 touches
3 conflicts

0x948836ff…59ab

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

10 conflicts on slot 0x90bbbcedf9…dddac6

← previous block·next block →recent activity