← previous blocknext block →recent activity

Analyzing

Block #102,218,739

25 transactions · 25 stateful · 2026-09-05 15:20:35 UTC

Parallelism

60/100

Blocked

44%

Avg conflicts / tx

1.68

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #102,218,739  ·  25 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0xe108b282…58b3

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0x256918f1…c4d0

0x34b655…2a6f

10 touches
10 conflicts

0x00000000…002f

0x1b6862…e19c

8 touches
6 conflicts

0x3a3097d7…2ab9

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

21 conflicts on slot 0xe108b28272…6558b3

← previous block·next block →recent activity