← previous blocknext block →recent activity

Analyzing

Block #100,892,490

21 transactions · 18 stateful · 2026-08-31 23:55:25 UTC

Parallelism

86/100

Blocked

33%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,892,490  ·  21 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

0x00000000…004c

0x80c745…7210

6 touches
3 conflicts

0xddbd58bd…0f52

0x065c9d…c394

6 touches
3 conflicts

0x25328c82…bc66

0x065c9d…c394

5 touches
3 conflicts

0x00000000…004f

0x80c745…7210

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x0778475b…bd75

0x2a68ba…90c5

4 touches
1 conflict

0xb87af72a…aef6

0x2a68ba…90c5

4 touches
1 conflict

0x22e0cc1d…ad0d

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: 0x80c74517…647210

3 conflicts on slot 0x0000000000…00004c

← previous block·next block →recent activity