← previous blocknext block →recent activity

Analyzing

Block #108,403,506

20 transactions · 17 stateful · 2026-09-27 07:17:34 UTC

Parallelism

70/100

Blocked

47%

Avg conflicts / tx

1.1

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #108,403,506  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xf5dc501b…831c

0x34b655…2a6f

10 touches
10 conflicts

0x7bd229ad…63b2

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xa69bb4e1…f2bb

0x34b655…2a6f

6 touches
3 conflicts

0x8ffa3328…ce11

0xe52b14…7230

4 touches
1 conflict

0x3053ffcc…717e

0x34b655…2a6f

4 touches
1 conflict

0xf79df061…e005

0xe52b14…7230

4 touches
1 conflict

0x9b419d78…018b

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

10 conflicts on slot 0xf5dc501bf7…74831c

← previous block·next block →recent activity