← previous blocknext block →recent activity

Analyzing

Block #108,989,102

18 transactions · 18 stateful · 2026-09-29 08:30:31 UTC

Parallelism

61/100

Blocked

50%

Avg conflicts / tx

1.06

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #108,989,102  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x23769ebc…c8ed

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xc2fae047…00f1

0x34b655…2a6f

8 touches
6 conflicts

0x508174fb…94d2

0x34b655…2a6f

8 touches
6 conflicts

0x6235638c…643c

0x1b6862…e19c

6 touches
3 conflicts

0xcb45d9d6…cb86

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x46483cb1…e7ca

0x34b655…2a6f

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 0x23769ebc9a…0ec8ed

← previous block·next block →recent activity