← previous blocknext block →recent activity

Analyzing

Block #107,816,512

23 transactions · 18 stateful · 2026-09-25 06:03:20 UTC

Parallelism

78/100

Blocked

39%

Avg conflicts / tx

0.7

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #107,816,512  ·  23 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

0x49890ced…6f23

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…0015

0x1b6862…e19c

6 touches
3 conflicts

0x9ac040c1…8226

0x1b6862…e19c

6 touches
3 conflicts

0x00000000…0013

0x1b6862…e19c

6 touches
3 conflicts

0x4cd7fdf4…7197

0x34b655…2a6f

6 touches
3 conflicts

0xfd2f61b3…a8bc

0x34b655…2a6f

6 touches
3 conflicts

0xcb2df07b…732d

0x34b655…2a6f

6 touches
3 conflicts

0x5cf4d55d…c588

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

10 conflicts on slot 0x49890ced8d…316f23

← previous block·next block →recent activity