← previous blocknext block →recent activity

Analyzing

Block #102,567,693

23 transactions · 21 stateful · 2026-09-06 20:49:04 UTC

Parallelism

78/100

Blocked

33%

Avg conflicts / tx

0.57

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,567,693  ·  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

0x00000000…0002

0xf5b5f7…6d70

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…002e

0x1b6862…e19c

4 touches
1 conflict

0x6d43ee99…bdd9

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0x90a021f0…f922

0x34b655…2a6f

4 touches
1 conflict

0x93f1d5e2…9290

0x34b655…2a6f

4 touches
1 conflict

0xcd31008f…f7b7

0x34b655…2a6f

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: 0xf5b5f7f8…a36d70

10 conflicts on slot 0x0000000000…000002

← previous block·next block →recent activity