← previous blocknext block →recent activity

Analyzing

Block #102,253,861

20 transactions · 17 stateful · 2026-09-05 18:18:34 UTC

Parallelism

60/100

Blocked

71%

Avg conflicts / tx

1.8

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,253,861  ·  20 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

0xa9d11061…b7e9

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x42bc00b9…1ee7

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…001f

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 conflicts

0x17a7f697…dcb8

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0012

0x1b6862…e19c

8 touches
6 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

28 conflicts on slot 0xa9d110613e…d3b7e9

← previous block·next block →recent activity