← previous blocknext block →recent activity

Analyzing

Block #102,358,917

16 transactions · 16 stateful · 2026-09-06 03:10:56 UTC

Parallelism

69/100

Blocked

50%

Avg conflicts / tx

1

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,358,917  ·  16 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

0x4ac4a2c2…2707

0x34b655…2a6f

8 touches
6 conflicts

0xc781e6bf…8fc9

0x34b655…2a6f

8 touches
6 conflicts

0x8fbd1a7e…17e4

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xa9af9157…5a6e

0x34b655…2a6f

8 touches
6 conflicts

0x10c19272…7441

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

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 0x4ac4a2c2e0…f32707

← previous block·next block →recent activity