← previous blocknext block →recent activity

Analyzing

Block #108,444,458

17 transactions · 16 stateful · 2026-09-27 10:43:42 UTC

Parallelism

76/100

Blocked

38%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #108,444,458  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x518b8dce…6d60

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x1045386d…cb89

0x1b6862…e19c

4 touches
1 conflict

0x1ad8153e…06bf

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x4292a836…9ed5

0x34b655…2a6f

4 touches
1 conflict

0x5086c64a…28ba

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 0x518b8dce2e…7e6d60

← previous block·next block →recent activity