← previous blocknext block →recent activity

Analyzing

Block #107,666,702

26 transactions · 24 stateful · 2026-09-24 17:28:29 UTC

Parallelism

92/100

Blocked

21%

Avg conflicts / tx

0.19

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #107,666,702  ·  26 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x662d9b98…0f6b

0x34b655…2a6f

4 touches
1 conflict

0x7bd229ad…63b2

0x34b655…2a6f

4 touches
1 conflict

0xf51a94f0…f9b9

0x34b655…2a6f

4 touches
1 conflict

0xf5dc501b…831c

0x34b655…2a6f

4 touches
1 conflict

0x11a462c7…2ccb

0x34b655…2a6f

4 touches
1 conflict

0x122a4e67…118d

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

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

1 conflict on slot 0x6d1b72eefe…416b78

← previous block·next block →recent activity