← previous blocknext block →recent activity

Analyzing

Block #108,962,300

24 transactions · 20 stateful · 2026-09-29 06:15:00 UTC

Parallelism

79/100

Blocked

35%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #108,962,300  ·  24 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

0xf30b9357…2e1e

0x34b655…2a6f

8 touches
6 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x50a9a003…4bb4

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 conflicts

0xc0b53c4b…7c8f

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…001e

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002e

0x1b6862…e19c

8 touches
6 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 0xf30b935720…582e1e

← previous block·next block →recent activity