← previous blocknext block →recent activity

Analyzing

Block #102,860,614

19 transactions · 18 stateful · 2026-09-07 21:28:08 UTC

Parallelism

84/100

Blocked

33%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #102,860,614  ·  19 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x261cbea7…e35d

0x34b655…2a6f

6 touches
3 conflicts

0xbd590df7…9891

0x34b655…2a6f

6 touches
3 conflicts

0xe1c4e5ce…0dec

0x34b655…2a6f

6 touches
3 conflicts

0x3c4b8fbd…9354

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x48b13e5e…3c2a

0x34b655…2a6f

4 touches
1 conflict

0x5f60264d…a5ba

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

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

3 conflicts on slot 0x261cbea79d…12e35d

← previous block·next block →recent activity