← previous blocknext block →recent activity

Analyzing

Block #101,089,168

21 transactions · 19 stateful · 2026-09-01 16:25:13 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #101,089,168  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0xe2de1aea…8024

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0x9a786711…5b52

0x34b655…2a6f

4 touches
1 conflict

0xf41c8ad9…9136

0xd32edf…ff58

3 touches
1 conflict

0x00f245ce…1e10

0x34b655…2a6f

2 touches
0 conflicts

0x0a8eb4ac…eba4

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity