← previous blocknext block →recent activity

Analyzing

Block #101,656,851

18 transactions · 16 stateful · 2026-09-03 16:01:18 UTC

Parallelism

61/100

Blocked

56%

Avg conflicts / tx

1.11

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #101,656,851  ·  18 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xd366e32f…ec19

0xa7283d…0ace

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x8fa7a69c…8fd7

0x7b5b07…6d63

6 touches
3 conflicts

0x00000000…0002

0xa7283d…0ace

6 touches
3 conflicts

0xd366e32f…ec16

0xa7283d…0ace

6 touches
3 conflicts

0xd366e32f…ec17

0xa7283d…0ace

6 touches
3 conflicts

0xd366e32f…ec18

0xa7283d…0ace

6 touches
3 conflicts

0x22e0cc1d…ad0d

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: Nad.fun: BONDING_CURVE

3 conflicts on slot 0xd366e32ff3…42ec19

← previous block·next block →recent activity