← previous blocknext block →recent activity

Analyzing

Block #108,940,124

26 transactions · 18 stateful · 2026-09-29 04:22:41 UTC

Parallelism

62/100

Blocked

61%

Avg conflicts / tx

1.54

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #108,940,124  ·  26 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

0xca841faa…486a

0x34b655…2a6f

18 touches
36 conflicts

0x945d1dbe…e1d7

0xc8689a…ee79

8 touches
6 conflicts

0x1faeed20…190f

0x34b655…2a6f

8 touches
6 conflicts

0x5ad5e6de…e7ad

0x34b655…2a6f

8 touches
6 conflicts

0x88fc2a68…3918

0x34b655…2a6f

8 touches
6 conflicts

0x8b780b26…f5ff

0x34b655…2a6f

8 touches
6 conflicts

0xada087b9…4aca

0x34b655…2a6f

8 touches
6 conflicts

0xb3af6b7b…bba9

0x34b655…2a6f

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

36 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity