← previous blocknext block →recent activity

Analyzing

Block #108,503,474

29 transactions · 27 stateful · 2026-09-27 15:40:48 UTC

Parallelism

66/100

Blocked

48%

Avg conflicts / tx

2.03

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #108,503,474  ·  29 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x945d1dbe…e1d7

0xc8689a…ee79

16 touches
28 conflicts

0xccc352f8…deda

0xd32edf…ff58

15 touches
28 conflicts

0x00000000…0015

0x1b6862…e19c

12 touches
15 conflicts

0x4c29ecd5…58b6

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…0013

0x1b6862…e19c

12 touches
15 conflicts

0xf8480e2a…dff2

0x1b6862…e19c

12 touches
15 conflicts

0x00000000…001c

0x1b6862…e19c

10 touches
10 conflicts

0x22badbc6…4c24

0x34b655…2a6f

10 touches
10 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: Settlement / Helper

28 conflicts on slot 0x945d1dbe12…30e1d7

← previous block·next block →recent activity