← previous blocknext block →recent activity

Analyzing

Block #100,023,679

11 transactions · 11 stateful · 2026-08-28 22:59:35 UTC

Parallelism

73/100

Blocked

27%

Avg conflicts / tx

0.36

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,023,679  ·  11 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

0x4f46a4fb…3224

0x34b655…2a6f

6 touches
3 conflicts

0x9816fc81…4f3d

0x34b655…2a6f

4 touches
1 conflict

0xb9b077a8…e029

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd1b40f29…9b9d

0x34b655…2a6f

4 touches
1 conflict

0xfcc8f826…7c5f

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xfe692697…7723

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 0x4f46a4fb0e…a43224

← previous block·next block →recent activity