← previous blocknext block →recent activity

Analyzing

Block #100,636,062

21 transactions · 18 stateful · 2026-08-31 02:25:06 UTC

Parallelism

76/100

Blocked

44%

Avg conflicts / tx

0.71

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #100,636,062  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x89999c15…fdac

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xcaa5e459…c7eb

0x34b655…2a6f

6 touches
3 conflicts

0xb74eef30…9e4e

0x34b655…2a6f

6 touches
3 conflicts

0x5086c64a…28ba

0x34b655…2a6f

4 touches
1 conflict

0x7db78f05…2895

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

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 0xc824469a90…af6425

← previous block·next block →recent activity