← previous blocknext block →recent activity

Analyzing

Block #100,022,008

18 transactions · 17 stateful · 2026-08-28 22:51:10 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

0.72

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,022,008  ·  18 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xafc57270…dd59

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x15698ac9…2a46

0x34b655…2a6f

6 touches
3 conflicts

0xa1731f0f…1f9d

0x34b655…2a6f

6 touches
3 conflicts

0x52d77b92…60e3

0x34b655…2a6f

4 touches
1 conflict

0x5f46663c…b4c2

0x34b655…2a6f

4 touches
1 conflict

0x85a88798…f85e

0x34b655…2a6f

4 touches
1 conflict

0xb06fd632…44de

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 0xafc5727015…d8dd59

← previous block·next block →recent activity