← previous blocknext block →recent activity

Analyzing

Block #101,325,351

23 transactions · 21 stateful · 2026-09-02 12:13:25 UTC

Parallelism

83/100

Blocked

29%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

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

0xb75367ff…a2b7

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…126f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x4dd2a831…bd5d

0x34b655…2a6f

4 touches
1 conflict

0x55ae04f8…2aaf

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7dd96c96…7335

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 0xb75367ffdb…6fa2b7

← previous block·next block →recent activity