← previous blocknext block →recent activity

Analyzing

Block #100,584,842

25 transactions · 23 stateful · 2026-08-30 22:07:26 UTC

Parallelism

88/100

Blocked

26%

Avg conflicts / tx

0.4

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,584,842  ·  25 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

0xb4c703ab…f8cf

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x9ff4ca89…6115

0x34b655…2a6f

6 touches
3 conflicts

0x258fcaf5…2084

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x9e70dadd…810d

0x34b655…2a6f

4 touches
1 conflict

0x9e70dadd…810e

0x34b655…2a6f

4 touches
1 conflict

0xf38a3927…ad62

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 0xb4c703ab76…fdf8cf

← previous block·next block →recent activity