← previous blocknext block →recent activity

Analyzing

Block #99,211,686

25 transactions · 23 stateful · 2026-08-26 02:38:22 UTC

Parallelism

56/100

Blocked

48%

Avg conflicts / tx

1.44

Longest chain

11 deep

Execution timeline

did this block parallelize well?

view

block #99,211,686  ·  25 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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xb2d8af24…4750

0x34b655…2a6f

8 touches
6 conflicts

0x731d7308…fd26

0x34b655…2a6f

6 touches
3 conflicts

0xd9c91db3…8ac8

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x261cbea7…e35d

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity