← previous blocknext block →recent activity

Analyzing

Block #101,922,639

21 transactions · 21 stateful · 2026-09-04 14:19:29 UTC

Parallelism

48/100

Blocked

62%

Avg conflicts / tx

2

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #101,922,639  ·  21 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0x39ccd26a…4654

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x555ab483…e847

0x34b655…2a6f

8 touches
6 conflicts

0xcf4590de…01cd

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xe4c6b0cb…0a20

0x1b6862…e19c

6 touches
3 conflicts

0x556beb43…e627

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 0x39ccd26aaf…a04654

← previous block·next block →recent activity