← previous blocknext block →recent activity

Analyzing

Block #100,565,431

22 transactions · 20 stateful · 2026-08-30 20:29:47 UTC

Parallelism

82/100

Blocked

45%

Avg conflicts / tx

0.64

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,565,431  ·  22 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x21a1d259…eda5

0x34b655…2a6f

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x595839b9…ca61

0x2b46c0…1669

4 touches
1 conflict

0x7aa91b8f…d070

0x2b46c0…1669

4 touches
1 conflict

0x8cf3d245…1d0d

0x2b46c0…1669

4 touches
1 conflict

0xe2263bea…6a9d

0x2b46c0…1669

4 touches
1 conflict

0xe2263bea…6a9e

0x2b46c0…1669

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 0x21a1d2596d…58eda5

← previous block·next block →recent activity