← previous blocknext block →recent activity

Analyzing

Block #109,229,202

30 transactions · 28 stateful · 2026-09-30 04:40:59 UTC

Parallelism

73/100

Blocked

61%

Avg conflicts / tx

1.33

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #109,229,202  ·  30 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x7d9ef283…ddd1

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x469854ac…edcd

0x34b655…2a6f

8 touches
6 conflicts

0x945d1dbe…e1d7

0xc8689a…ee79

8 touches
6 conflicts

0x1032f16c…a9b1

0x34b655…2a6f

8 touches
6 conflicts

0x3243e72f…1f6d

0x34b655…2a6f

8 touches
6 conflicts

0x6d5d1fb5…86a7

0x34b655…2a6f

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity