← previous blocknext block →recent activity

Analyzing

Block #102,313,766

22 transactions · 21 stateful · 2026-09-05 23:22:10 UTC

Parallelism

64/100

Blocked

43%

Avg conflicts / tx

0.86

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #102,313,766  ·  22 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

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x84f1799f…9466

0x34b655…2a6f

6 touches
3 conflicts

0x42e5184f…4e8b

0x34b655…2a6f

6 touches
3 conflicts

0x5d1ac445…5233

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

6 touches
3 conflicts

0xbceecf11…0120

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 0x482471adbb…39122f

← previous block·next block →recent activity