← previous blocknext block →recent activity

Analyzing

Block #100,629,716

20 transactions · 12 stateful · 2026-08-31 01:53:10 UTC

Parallelism

85/100

Blocked

42%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #100,629,716  ·  20 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

6 touches
3 conflicts

0x00000000…004c

0x80c745…7210

4 touches
1 conflict

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x5b6af007…0f35

0x34b655…2a6f

4 touches
1 conflict

0x5d116df7…de83

0x34b655…2a6f

4 touches
1 conflict

0x83f3d320…fb59

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

3 conflicts on slot 0x261cbea79d…12e35d

← previous block·next block →recent activity