← previous blocknext block →recent activity

Analyzing

Block #100,616,149

19 transactions · 17 stateful · 2026-08-31 00:44:56 UTC

Parallelism

89/100

Blocked

18%

Avg conflicts / tx

0.16

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #100,616,149  ·  19 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xfe888b58…0411

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x1408a100…f721

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x24405386…285a

0x34b655…2a6f

4 touches
1 conflict

0x4edbf2d2…36bc

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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

1 conflict on slot 0xfe888b58fc…620411

← previous block·next block →recent activity