← previous blocknext block →recent activity

Analyzing

Block #100,849,225

17 transactions · 17 stateful · 2026-08-31 20:17:48 UTC

Parallelism

71/100

Blocked

41%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,849,225  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x34f96536…244a

0x34b655…2a6f

6 touches
3 conflicts

0xab60dc09…85e4

0x34b655…2a6f

6 touches
3 conflicts

0xe61a3df2…f763

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…001b

0x1b6862…e19c

4 touches
1 conflict

0x00000000…002b

0x1b6862…e19c

4 touches
1 conflict

0x5a3732cb…edaf

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xaad6be10…0801

0x2a68ba…90c5

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 0x34f96536af…bc244a

← previous block·next block →recent activity