← previous blocknext block →recent activity

Analyzing

Block #101,895,570

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

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #101,895,570  ·  20 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

0x898a08aa…c855

0x34b655…2a6f

6 touches
3 conflicts

0x8bf661cb…bcd2

0x34b655…2a6f

6 touches
3 conflicts

0x9c088939…ddd7

0x34b655…2a6f

6 touches
3 conflicts

0x5c7b5ec0…0764

0x34b655…2a6f

6 touches
3 conflicts

0x67043b0b…97d7

0x34b655…2a6f

6 touches
3 conflicts

0xaaf36ccb…f35c

0x34b655…2a6f

6 touches
3 conflicts

0xd4f6a526…ad10

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 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

3 conflicts on slot 0x898a08aa11…0cc855

← previous block·next block →recent activity