← previous blocknext block →recent activity

Analyzing

Block #108,840,237

21 transactions · 16 stateful · 2026-09-28 19:58:29 UTC

Parallelism

71/100

Blocked

63%

Avg conflicts / tx

1.24

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #108,840,237  ·  21 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf5dc501b…831c

0x34b655…2a6f

12 touches
15 conflicts

0x7bd229ad…63b2

0x34b655…2a6f

12 touches
15 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xd739490d…821e

0x34b655…2a6f

10 touches
10 conflicts

0x10a62de8…1068

0xd32edf…ff58

9 touches
10 conflicts

0x00000000…002b

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0054

0x1b6862…e19c

8 touches
6 conflicts

0x5c421c70…c2ee

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

15 conflicts on slot 0xf5dc501bf7…74831c

← previous block·next block →recent activity