← previous blocknext block →recent activity

Analyzing

Block #101,019,844

27 transactions · 21 stateful · 2026-09-01 10:36:06 UTC

Parallelism

70/100

Blocked

43%

Avg conflicts / tx

0.96

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #101,019,844  ·  27 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

0x00e3ad8d…76a8

0x34b655…2a6f

12 touches
15 conflicts

0xb3aa2022…9e09

0x34b655…2a6f

12 touches
15 conflicts

0xa9988419…9f45

0x34b655…2a6f

10 touches
10 conflicts

0xcff8ef6e…c88e

0x34b655…2a6f

8 touches
6 conflicts

0x7c51d9aa…af39

0x34b655…2a6f

8 touches
6 conflicts

0x42522e76…2592

0x34b655…2a6f

8 touches
6 conflicts

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x451e482b…7e7d

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 0x00e3ad8d71…6876a8

← previous block·next block →recent activity