← previous blocknext block →recent activity

Analyzing

Block #100,753,026

24 transactions · 21 stateful · 2026-08-31 12:13:27 UTC

Parallelism

71/100

Blocked

43%

Avg conflicts / tx

0.88

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,753,026  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x2bf5fd14…a7ad

0x34b655…2a6f

10 touches
10 conflicts

0x81716ce9…095f

0x34b655…2a6f

8 touches
6 conflicts

0x26dc3732…c567

0x34b655…2a6f

6 touches
3 conflicts

0xef048f92…572b

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x326a02b5…8dad

0x34b655…2a6f

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x950d31b1…dfcc

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 0x2bf5fd14a8…eba7ad

← previous block·next block →recent activity