← previous blocknext block →recent activity

Analyzing

Block #107,785,468

16 transactions · 15 stateful · 2026-09-25 03:26:57 UTC

Parallelism

75/100

Blocked

47%

Avg conflicts / tx

0.69

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #107,785,468  ·  16 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

0xa0a8c7a5…3422

0x34b655…2a6f

8 touches
6 conflicts

0x3ce9daa8…d4ac

0x34b655…2a6f

8 touches
6 conflicts

0xdeaa385f…6b8b

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xaae6463e…bfcc

0x34b655…2a6f

8 touches
6 conflicts

0xd53220ed…473a

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x12b6bc1a…6962

0x34b655…2a6f

6 touches
3 conflicts

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 0xa0a8c7a55a…e73422

← previous block·next block →recent activity