← previous blocknext block →recent activity

Analyzing

Block #108,278,768

22 transactions · 22 stateful · 2026-09-26 20:49:52 UTC

Parallelism

68/100

Blocked

45%

Avg conflicts / tx

1.23

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #108,278,768  ·  22 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

0xca841faa…486a

0x34b655…2a6f

14 touches
21 conflicts

0x945d1dbe…e1d7

0xc8689a…ee79

12 touches
15 conflicts

0x5969523e…5191

0x34b655…2a6f

12 touches
15 conflicts

0x9daafdf9…bb53

0x34b655…2a6f

12 touches
15 conflicts

0xbc8fb280…76a3

0x34b655…2a6f

12 touches
15 conflicts

0xd874dcbe…381c

0x34b655…2a6f

12 touches
15 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

12 touches
15 conflicts

0xe226a0be…c046

0x34b655…2a6f

12 touches
15 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

21 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity