← previous blocknext block →recent activity

Analyzing

Block #101,657,765

18 transactions · 16 stateful · 2026-09-03 16:05:54 UTC

Parallelism

61/100

Blocked

44%

Avg conflicts / tx

1.67

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #101,657,765  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x20b1228b…2487

0x34b655…2a6f

8 touches
6 conflicts

0xb409e204…89ac

0x34b655…2a6f

8 touches
6 conflicts

0xc6615a36…3cf0

0x34b655…2a6f

6 touches
3 conflicts

0xcd5c0ecb…4b5f

0x34b655…2a6f

6 touches
3 conflicts

0x033ddbe8…850a

0x34b655…2a6f

5 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

21 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity