← previous blocknext block →recent activity

Analyzing

Block #108,680,405

19 transactions · 18 stateful · 2026-09-28 06:31:48 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1.21

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #108,680,405  ·  19 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

0x92cdf25f…8e40

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x2130a548…c1de

0x34b655…2a6f

8 touches
6 conflicts

0x23769ebc…c8ed

0x34b655…2a6f

8 touches
6 conflicts

0xef5959a3…2a2f

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xfe65bb7b…12d7

0x34b655…2a6f

4 touches
1 conflict

0x08cc68a2…2a59

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

15 conflicts on slot 0x92cdf25f2c…0f8e40

← previous block·next block →recent activity