← previous blocknext block →recent activity

Analyzing

Block #99,477,710

24 transactions · 18 stateful · 2026-08-27 00:57:28 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.38

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,477,710  ·  24 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

0x64275949…d698

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd814f518…f5b4

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xcc70e9ba…42a0

0x34b655…2a6f

4 touches
1 conflict

0x40a9339c…6571

0x34b655…2a6f

4 touches
1 conflict

0x310a7246…2dcb

0x34b655…2a6f

4 touches
1 conflict

0xd6113c0f…0a4b

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 0x6427594999…6ed698

← previous block·next block →recent activity