← previous blocknext block →recent activity

Analyzing

Block #106,917,324

15 transactions · 15 stateful · 2026-09-22 02:34:56 UTC

Parallelism

73/100

Blocked

53%

Avg conflicts / tx

1

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #106,917,324  ·  15 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

0x81d2de5b…f95e

0x34b655…2a6f

8 touches
6 conflicts

0xe720a4c6…8eb0

0x34b655…2a6f

8 touches
6 conflicts

0x23769ebc…c8ed

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…002d

0x1b6862…e19c

6 touches
3 conflicts

0x2b093939…9088

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…001d

0x1b6862…e19c

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

6 conflicts on slot 0x81d2de5b67…d3f95e

← previous block·next block →recent activity