← previous blocknext block →recent activity

Analyzing

Block #100,790,259

22 transactions · 21 stateful · 2026-08-31 15:20:56 UTC

Parallelism

86/100

Blocked

29%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,790,259  ·  22 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

0x00000000…0002

0xf5b5f7…6d70

4 touches
1 conflict

0x598a6a32…d1ae

0x34b655…2a6f

4 touches
1 conflict

0x6caf33e2…c261

0x34b655…2a6f

4 touches
1 conflict

0x831f75b4…945d

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x00000000…004b

0x80c745…7210

4 touches
1 conflict

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

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: 0xf5b5f7f8…a36d70

1 conflict on slot 0x0000000000…000002

← previous block·next block →recent activity