← previous blocknext block →recent activity

Analyzing

Block #102,810,166

26 transactions · 22 stateful · 2026-09-07 17:14:11 UTC

Parallelism

69/100

Blocked

68%

Avg conflicts / tx

1.58

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,810,166  ·  26 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xaad6be10…0801

0x2a68ba…90c5

12 touches
15 conflicts

0x00000000…003d

0x065c9d…c394

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x7aad02c6…b979

0x34b655…2a6f

8 touches
6 conflicts

0x6fcd6eb8…d54a

0x065c9d…c394

7 touches
6 conflicts

0x892daf6e…48d8

0x065c9d…c394

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x80de6d4b…8ce5

0xd32edf…ff58

5 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: Kuru Exchange: MarginAccount

15 conflicts on slot 0xaad6be10ae…2c0801

← previous block·next block →recent activity