← previous blocknext block →recent activity

Analyzing

Block #101,922,532

26 transactions · 25 stateful · 2026-09-04 14:18:56 UTC

Parallelism

73/100

Blocked

40%

Avg conflicts / tx

0.92

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #101,922,532  ·  26 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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xfa805f95…72a4

0x34b655…2a6f

8 touches
6 conflicts

0x897879a1…9c78

0x34b655…2a6f

8 touches
6 conflicts

0xc853be2d…b18f

0x34b655…2a6f

8 touches
6 conflicts

0x32e1d03e…68a7

0x34b655…2a6f

8 touches
6 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

8 touches
6 conflicts

0x169fd56e…b092

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 0xc824469a90…af6425

← previous block·next block →recent activity