← previous blocknext block →recent activity

Analyzing

Block #108,961,509

21 transactions · 20 stateful · 2026-09-29 06:10:54 UTC

Parallelism

62/100

Blocked

55%

Avg conflicts / tx

1.52

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #108,961,509  ·  21 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

14 touches
21 conflicts

0x8b780b26…f5ff

0x34b655…2a6f

10 touches
10 conflicts

0x945d1dbe…e1d7

0xc8689a…ee79

6 touches
3 conflicts

0xba38536d…2b7d

0x065c9d…c394

6 touches
3 conflicts

0x0121c33f…8b6a

0x34b655…2a6f

6 touches
3 conflicts

0x5ad5e6de…e7ad

0x34b655…2a6f

6 touches
3 conflicts

0x88fc2a68…3918

0x34b655…2a6f

6 touches
3 conflicts

0xada087b9…4aca

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

21 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity