← previous blocknext block →recent activity

Analyzing

Block #99,957,462

31 transactions · 30 stateful · 2026-08-28 17:26:07 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.42

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,957,462  ·  31 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

0x5fad6fee…7714

0x34b655…2a6f

8 touches
6 conflicts

0x9d3e7236…49e2

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x69ee34d1…30f8

0x34b655…2a6f

6 touches
3 conflicts

0x5e78b449…521d

0xd32edf…ff58

5 touches
3 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

4 touches
1 conflict

0xe483d4e3…e52d

0x1b6862…e19c

4 touches
1 conflict

0x0d85683a…ecd8

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 0x5fad6fee64…277714

← previous block·next block →recent activity