← previous blocknext block →recent activity

Analyzing

Block #101,323,930

20 transactions · 18 stateful · 2026-09-02 12:06:16 UTC

Parallelism

80/100

Blocked

39%

Avg conflicts / tx

0.6

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,323,930  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x89999c15…fdac

0x34b655…2a6f

4 touches
1 conflict

0xcd3fd9c1…dcc0

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x36126dcb…ca1e

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35d

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

3 conflicts on slot 0xbde524f475…b143bf

← previous block·next block →recent activity