← previous blocknext block →recent activity

Analyzing

Block #100,021,045

21 transactions · 18 stateful · 2026-08-28 22:46:19 UTC

Parallelism

81/100

Blocked

33%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #100,021,045  ·  21 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x54f7f60f…43cc

0x34b655…2a6f

4 touches
1 conflict

0x5e782d17…5317

0x34b655…2a6f

4 touches
1 conflict

0x7d0eaae2…60b7

0x34b655…2a6f

4 touches
1 conflict

0x990bf0c1…a307

0x34b655…2a6f

4 touches
1 conflict

0x9ff4ca89…6115

0x34b655…2a6f

4 touches
1 conflict

0xbc12e07e…bf7a

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

← previous block·next block →recent activity