← previous blocknext block →recent activity

Analyzing

Block #101,924,261

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

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

0.9

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #101,924,261  ·  21 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

0xb75367ff…a2b7

0x34b655…2a6f

12 touches
15 conflicts

0x51fc8795…126f

0x34b655…2a6f

12 touches
15 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

10 touches
10 conflicts

0xcb10192b…9066

0x34b655…2a6f

10 touches
10 conflicts

0xa1a01ded…c087

0x34b655…2a6f

8 touches
6 conflicts

0xa735de1d…29b0

0x34b655…2a6f

8 touches
6 conflicts

0x9bff3222…a246

0x34b655…2a6f

8 touches
6 conflicts

0x762a21b1…4242

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 0xb75367ffdb…6fa2b7

← previous block·next block →recent activity