← previous blocknext block →recent activity

Analyzing

Block #100,979,087

28 transactions · 23 stateful · 2026-09-01 07:11:00 UTC

Parallelism

79/100

Blocked

30%

Avg conflicts / tx

0.36

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #100,979,087  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x6b4edd58…9623

0x34b655…2a6f

6 touches
3 conflicts

0x0b3eb43a…ca08

0x34b655…2a6f

4 touches
1 conflict

0x14fe1598…d0ba

0x34b655…2a6f

4 touches
1 conflict

0x191e0467…70e5

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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