← previous blocknext block →recent activity

Analyzing

Block #109,162,049

20 transactions · 17 stateful · 2026-09-29 23:03:00 UTC

Parallelism

75/100

Blocked

53%

Avg conflicts / tx

0.95

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #109,162,049  ·  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

0x0505bae8…b4fb

0x34b655…2a6f

8 touches
6 conflicts

0xba9f9225…2ead

0x34b655…2a6f

8 touches
6 conflicts

0x5da69359…aada

0x34b655…2a6f

8 touches
6 conflicts

0xc65c515b…5a02

0xd32edf…ff58

7 touches
6 conflicts

0x00000000…002a

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0040

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0053

0x1b6862…e19c

6 touches
3 conflicts

0x063eca74…c2e2

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 0x0505bae898…14b4fb

← previous block·next block →recent activity