← previous blocknext block →recent activity

Analyzing

Block #108,482,961

26 transactions · 25 stateful · 2026-09-27 13:57:30 UTC

Parallelism

88/100

Blocked

24%

Avg conflicts / tx

0.27

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #108,482,961  ·  26 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xaf9ee035…8700

0x34b655…2a6f

4 touches
1 conflict

0xc2fe6ed6…f8be

0x34b655…2a6f

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x26253352…1a75

0x34b655…2a6f

4 touches
1 conflict

0x7b64a69f…f1fc

0x34b655…2a6f

4 touches
1 conflict

0x3b8da5cc…e045

0x34b655…2a6f

4 touches
1 conflict

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

3 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity