← previous blocknext block →recent activity

Analyzing

Block #99,357,938

21 transactions · 18 stateful · 2026-08-26 14:54:16 UTC

Parallelism

48/100

Blocked

72%

Avg conflicts / tx

2.38

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #99,357,938  ·  21 txs across 11 waves  ·  depth 11
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

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

0xca841faa…486a

0x34b655…2a6f

16 touches
28 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

10 touches
10 conflicts

0x17ff2059…ddb4

0x34b655…2a6f

8 touches
6 conflicts

0x6e3e9f18…f684

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x5a548af5…0eb0

0x34b655…2a6f

6 touches
3 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

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

28 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity