← previous blocknext block →recent activity

Analyzing

Block #100,046,765

22 transactions · 21 stateful · 2026-08-29 00:55:47 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,046,765  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xb240b520…a88a

0x34b655…2a6f

8 touches
6 conflicts

0xce485734…7ac7

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x2c2db8e9…fdc7

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x53ca1284…cb2c

0x34b655…2a6f

4 touches
1 conflict

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

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 0xb240b520db…67a88a

← previous block·next block →recent activity