← previous blocknext block →recent activity

Analyzing

Block #100,787,061

27 transactions · 24 stateful · 2026-08-31 15:04:49 UTC

Parallelism

85/100

Blocked

25%

Avg conflicts / tx

0.26

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,787,061  ·  27 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

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x08e8f2c9…a11a

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xccebf5c5…8758

0x34b655…2a6f

4 touches
1 conflict

0xd2dfd9bc…3eec

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xf495bdbf…6315

0x34b655…2a6f

4 touches
1 conflict

0xee4c8bea…dcc6

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 0xca841faae5…71486a

← previous block·next block →recent activity