← previous blocknext block →recent activity

Analyzing

Block #101,315,773

23 transactions · 19 stateful · 2026-09-02 11:25:14 UTC

Parallelism

78/100

Blocked

47%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,315,773  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x8571fbdb…345a

0x34b655…2a6f

8 touches
6 conflicts

0xc5847c4d…a65c

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x0725d33c…e296

0x34b655…2a6f

6 touches
3 conflicts

0x4979282b…2936

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x6a9e408e…3721

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

6 conflicts on slot 0x8571fbdb53…aa345a

← previous block·next block →recent activity