← previous blocknext block →recent activity

Analyzing

Block #100,267,957

20 transactions · 17 stateful · 2026-08-29 19:30:53 UTC

Parallelism

85/100

Blocked

29%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,267,957  ·  20 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

0x6caf33e2…c261

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x009a0451…b83e

0x34b655…2a6f

4 touches
1 conflict

0x00f6a8a7…0e6e

0x34b655…2a6f

4 touches
1 conflict

0x0e4000ee…afb9

0x34b655…2a6f

4 touches
1 conflict

0x117ee717…5c5c

0x34b655…2a6f

4 touches
1 conflict

0x5086c64a…28ba

0x34b655…2a6f

4 touches
1 conflict

0x56a284d9…32e4

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 0x6caf33e26f…3dc261

← previous block·next block →recent activity