← previous blocknext block →recent activity

Analyzing

Block #103,212,702

17 transactions · 17 stateful · 2026-09-09 03:02:06 UTC

Parallelism

76/100

Blocked

24%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #103,212,702  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xf38a3927…ad62

0x34b655…2a6f

4 touches
1 conflict

0xd9722304…6ed0

0x34b655…2a6f

4 touches
1 conflict

0xdc7b9eda…e616

0x34b655…2a6f

4 touches
1 conflict

0xe29e7f91…90ce

0x34b655…2a6f

4 touches
1 conflict

0xf1894e7f…30fe

0x34b655…2a6f

4 touches
1 conflict

0x290abc80…f605

0x34b655…2a6f

4 touches
1 conflict

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

6 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity