← previous blocknext block →recent activity

Analyzing

Block #100,162,384

21 transactions · 18 stateful · 2026-08-29 10:38:01 UTC

Parallelism

67/100

Blocked

39%

Avg conflicts / tx

0.71

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #100,162,384  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xe5bb3628…e5f1

0x34b655…2a6f

8 touches
6 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xb5cddf91…0abf

0x34b655…2a6f

6 touches
3 conflicts

0xb75d08b2…3e12

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0x23ef1567…8f31

0x34b655…2a6f

5 touches
3 conflicts

0xa4e9800f…4ab1

0x34b655…2a6f

4 touches
1 conflict

0xa801295f…7de6

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

6 conflicts on slot 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity