← previous blocknext block →recent activity

Analyzing

Block #100,226,377

17 transactions · 15 stateful · 2026-08-29 16:00:08 UTC

Parallelism

65/100

Blocked

53%

Avg conflicts / tx

1.18

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,226,377  ·  17 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

0xca841faa…486a

0x34b655…2a6f

12 touches
15 conflicts

0x00000000…00c9

0x34b655…2a6f

4 touches
1 conflict

0x08e8f2c9…a11a

0x34b655…2a6f

4 touches
1 conflict

0x15698ac9…2a46

0x34b655…2a6f

4 touches
1 conflict

0x1b5d2e60…99b5

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x289a374c…7e94

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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

15 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity