← previous blocknext block →recent activity

Analyzing

Block #101,325,932

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

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #101,325,932  ·  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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x31519d10…f76b

0x34b655…2a6f

4 touches
1 conflict

0x7d8a419f…686a

0x34b655…2a6f

4 touches
1 conflict

0xa3c36de0…3cf3

0x34b655…2a6f

4 touches
1 conflict

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x00000000…001d

0x1b6862…e19c

2 touches
0 conflicts

0x00000000…002d

0x1b6862…e19c

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

6 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity