← previous blocknext block →recent activity

Analyzing

Block #100,085,658

28 transactions · 21 stateful · 2026-08-29 04:11:35 UTC

Parallelism

82/100

Blocked

38%

Avg conflicts / tx

0.5

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,085,658  ·  28 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x50c61506…343f

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0x065c9d…c394

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0xbb97db90…4c93

0xc8689a…ee79

4 touches
1 conflict

0x046a928e…0012

0x2a68ba…90c5

4 touches
1 conflict

0x02373c43…3cb3

0x34b655…2a6f

4 touches
1 conflict

0x2c2db8e9…fdc7

0x34b655…2a6f

4 touches
1 conflict

0x2cfe7c05…2b42

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 0x50c615063f…63343f

← previous block·next block →recent activity