← previous blocknext block →recent activity

Analyzing

Block #100,029,367

23 transactions · 19 stateful · 2026-08-28 23:28:13 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,029,367  ·  23 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x15698ac9…2a46

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x271ab0bd…7594

0x34b655…2a6f

4 touches
1 conflict

0x28aa8ed1…01e5

0x34b655…2a6f

4 touches
1 conflict

0x2999ebda…ce6c

0x34b655…2a6f

4 touches
1 conflict

0x5f46663c…b4c2

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