← previous blocknext block →recent activity

Analyzing

Block #100,875,562

28 transactions · 24 stateful · 2026-08-31 22:30:16 UTC

Parallelism

86/100

Blocked

25%

Avg conflicts / tx

0.25

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,875,562  ·  28 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xaad6be10…0801

0x2a68ba…90c5

4 touches
1 conflict

0x164a9ec4…99e8

0x34b655…2a6f

4 touches
1 conflict

0x1f00a5b3…bf76

0x34b655…2a6f

4 touches
1 conflict

0x450fb5b7…9760

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x56a2a8ed…51ad

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity