← previous blocknext block →recent activity

Analyzing

Block #100,049,893

17 transactions · 16 stateful · 2026-08-29 01:11:32 UTC

Parallelism

82/100

Blocked

25%

Avg conflicts / tx

0.24

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,049,893  ·  17 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

0x261cbea7…e35d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x36126dcb…ca1e

0x34b655…2a6f

4 touches
1 conflict

0x5af10b50…8d5c

0x34b655…2a6f

4 touches
1 conflict

0x7083c381…0ce7

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

0x34b655…2a6f

4 touches
1 conflict

0x8c387e3e…85b4

0x34b655…2a6f

4 touches
1 conflict

0xbd590df7…9891

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

1 conflict on slot 0x261cbea79d…12e35d

← previous block·next block →recent activity