← previous blocknext block →recent activity

Analyzing

Block #107,848,459

24 transactions · 17 stateful · 2026-09-25 08:44:07 UTC

Parallelism

79/100

Blocked

53%

Avg conflicts / tx

0.58

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,848,459  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xf75c3a6b…0568

0x34b655…2a6f

8 touches
6 conflicts

0x91220b8f…7a08

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x49890ced…6f23

0x34b655…2a6f

6 touches
3 conflicts

0xac107d6c…eb6f

0xd32edf…ff58

5 touches
3 conflicts

0x00670a56…27a0

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

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

6 conflicts on slot 0xf75c3a6bf5…da0568

← previous block·next block →recent activity