← previous blocknext block →recent activity

Analyzing

Block #108,103,441

24 transactions · 21 stateful · 2026-09-26 06:07:28 UTC

Parallelism

71/100

Blocked

52%

Avg conflicts / tx

1.13

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #108,103,441  ·  24 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

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x4757fc7b…70b7

0x34b655…2a6f

4 touches
1 conflict

0x556beb43…e627

0x34b655…2a6f

4 touches
1 conflict

0x5969523e…5191

0x34b655…2a6f

4 touches
1 conflict

0x5ad5e6de…e7ad

0x34b655…2a6f

4 touches
1 conflict

0x7aa463de…e7b8

0x34b655…2a6f

4 touches
1 conflict

0x7efbf74f…f9d2

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

21 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity