← previous blocknext block →recent activity

Analyzing

Block #100,229,364

18 transactions · 17 stateful · 2026-08-29 16:15:10 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.22

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,229,364  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x29cd05f5…390c

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x3f81bcfb…2905

0x40c49f…2af0

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5cbf2fd0…5777

0x34b655…2a6f

4 touches
1 conflict

0x6c40dcfd…a4e3

0x34b655…2a6f

4 touches
1 conflict

0xb3aa2022…9e09

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

10 conflicts on slot 0x29cd05f5e7…a9390c

← previous block·next block →recent activity