← previous blocknext block →recent activity

Analyzing

Block #102,285,563

22 transactions · 18 stateful · 2026-09-05 20:59:20 UTC

Parallelism

73/100

Blocked

50%

Avg conflicts / tx

0.82

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,285,563  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x109d8a52…a7b7

0x34b655…2a6f

8 touches
6 conflicts

0x53103bb4…02a1

0x34b655…2a6f

8 touches
6 conflicts

0x256918f1…c4d0

0x34b655…2a6f

8 touches
6 conflicts

0xe108b282…58b3

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…641f

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