← previous blocknext block →recent activity

Analyzing

Block #100,125,484

16 transactions · 15 stateful · 2026-08-29 07:32:06 UTC

Parallelism

81/100

Blocked

13%

Avg conflicts / tx

0.25

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,125,484  ·  16 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

0xc824469a…641f

0x34b655…2a6f

6 touches
3 conflicts

0x172b0de5…980b

0x34b655…2a6f

4 touches
1 conflict

0x5060cdde…445d

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

0x34b655…2a6f

4 touches
1 conflict

0x9a2d2edc…f7f8

0x34b655…2a6f

4 touches
1 conflict

0x9a8482cc…8bee

0x34b655…2a6f

4 touches
1 conflict

0x9cf9008a…d826

0x34b655…2a6f

4 touches
1 conflict

0xfb14d7f1…e509

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

3 conflicts on slot 0xc824469a90…af641f

← previous block·next block →recent activity