← previous blocknext block →recent activity

Analyzing

Block #102,529,855

26 transactions · 21 stateful · 2026-09-06 17:37:13 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.46

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #102,529,855  ·  26 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x256918f1…c4d0

0x34b655…2a6f

4 touches
1 conflict

0x28d5839f…9020

0x34b655…2a6f

4 touches
1 conflict

0x2acf7e76…bbe8

0x34b655…2a6f

4 touches
1 conflict

0x4635fb46…4cfd

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4a5956ef…e226

0x34b655…2a6f

4 touches
1 conflict

0x5eb187dd…b1d6

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 0xca841faae5…71486a

← previous block·next block →recent activity