← previous blocknext block →recent activity

Analyzing

Block #101,838,973

17 transactions · 17 stateful · 2026-09-04 07:17:21 UTC

Parallelism

88/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #101,838,973  ·  17 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5e8

0x34b655…2a6f

4 touches
1 conflict

0xe3684e08…c96a

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0012

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0013

0x1b6862…e19c

4 touches
1 conflict

0x00000000…0015

0x1b6862…e19c

4 touches
1 conflict

0x00000000…001f

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002f

0x1b6862…e19c

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

1 conflict on slot 0xbde524f475…b143bf

← previous block·next block →recent activity