← previous blocknext block →recent activity

Analyzing

Block #101,971,464

15 transactions · 14 stateful · 2026-09-04 18:27:09 UTC

Parallelism

73/100

Blocked

50%

Avg conflicts / tx

0.93

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,971,464  ·  15 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

0x51fc8795…126f

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xf5d28bce…c32c

0x34b655…2a6f

6 touches
3 conflicts

0x4dffc33e…068d

0x34b655…2a6f

6 touches
3 conflicts

0x5c7b5ec0…0764

0x34b655…2a6f

6 touches
3 conflicts

0x79ec4509…1f61

0x34b655…2a6f

6 touches
3 conflicts

0x7dd96c96…7335

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

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 0x51fc8795c8…57126f

← previous block·next block →recent activity