← previous blocknext block →recent activity

Analyzing

Block #100,605,769

34 transactions · 27 stateful · 2026-08-30 23:52:43 UTC

Parallelism

74/100

Blocked

41%

Avg conflicts / tx

0.91

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #100,605,769  ·  34 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd1450d8e…475b

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xa4c5f5b1…82f8

0x34b655…2a6f

8 touches
6 conflicts

0x2c2db8e9…fdc7

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5ed1f9d0…fc7f

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

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 0xd1450d8e36…0a475b

← previous block·next block →recent activity