← previous blocknext block →recent activity

Analyzing

Block #102,248,242

17 transactions · 17 stateful · 2026-09-05 17:50:06 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

1.06

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #102,248,242  ·  17 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

0xd66696e0…0842

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x5da92df7…74b5

0x34b655…2a6f

8 touches
6 conflicts

0x5d1ac445…5233

0x34b655…2a6f

8 touches
6 conflicts

0x14d1bf0e…e0a0

0x1b6862…e19c

6 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

6 touches
3 conflicts

0x183d9280…e5ec

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 0xd66696e0dc…230842

← previous block·next block →recent activity