← previous blocknext block →recent activity

Analyzing

Block #100,248,311

17 transactions · 13 stateful · 2026-08-29 17:51:14 UTC

Parallelism

82/100

Blocked

31%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,248,311  ·  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

0xdbd9d618…7b7f

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0xf2f76ab3…623e

0x2a68ba…90c5

4 touches
1 conflict

0x0221091a…da2a

0x34b655…2a6f

4 touches
1 conflict

0x6a8ffcda…0387

0x34b655…2a6f

4 touches
1 conflict

0x6ac4a9ce…5f63

0x34b655…2a6f

4 touches
1 conflict

0xacca1d4f…d6df

0x34b655…2a6f

4 touches
1 conflict

0xd2862d04…388c

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 0xdbd9d61803…2d7b7f

← previous block·next block →recent activity