← previous blocknext block →recent activity

Analyzing

Block #100,874,432

17 transactions · 17 stateful · 2026-08-31 22:24:35 UTC

Parallelism

82/100

Blocked

29%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,874,432  ·  17 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

0x6f132c01…cdcc

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x6f132c01…cdcd

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0xb1856468…e84f

0x34b655…2a6f

4 touches
1 conflict

0x7ae4f840…c886

0x065c9d…c394

3 touches
1 conflict

0xada087b9…4aca

0x34b655…2a6f

2 touches
0 conflicts

0xe2d50773…c39e

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0x6f132c01d5…7dcdcc

← previous block·next block →recent activity