← previous blocknext block →recent activity

Analyzing

Block #100,595,764

22 transactions · 20 stateful · 2026-08-30 23:02:22 UTC

Parallelism

73/100

Blocked

50%

Avg conflicts / tx

1.32

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,595,764  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x76622fb2…4f08

0x34b655…2a6f

12 touches
15 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x25180879…8191

0x34b655…2a6f

8 touches
6 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0x55192654…91fe

0x34b655…2a6f

6 touches
3 conflicts

0x502b3ee1…7f7c

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

15 conflicts on slot 0x76622fb2e3…024f08

← previous block·next block →recent activity