← previous blocknext block →recent activity

Analyzing

Block #101,067,062

22 transactions · 21 stateful · 2026-09-01 14:33:47 UTC

Parallelism

77/100

Blocked

38%

Avg conflicts / tx

0.68

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,067,062  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x70e677f5…e3bd

0x34b655…2a6f

8 touches
6 conflicts

0x5b657130…5cc7

0xd32edf…ff58

7 touches
6 conflicts

0x6f132c01…cdcc

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x6caf33e2…c261

0x34b655…2a6f

6 touches
3 conflicts

0x37699b20…106f

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x14b0d0e3…3f17

0x34b655…2a6f

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 0x70e677f5c0…90e3bd

← previous block·next block →recent activity