← previous blocknext block →recent activity

Analyzing

Block #99,615,122

22 transactions · 21 stateful · 2026-08-27 12:35:04 UTC

Parallelism

77/100

Blocked

33%

Avg conflicts / tx

0.73

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,615,122  ·  22 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x4be9812b…48a9

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x9c779a01…5191

0x34b655…2a6f

8 touches
6 conflicts

0x021cd478…a6d4

0x34b655…2a6f

6 touches
3 conflicts

0x8a02d049…f481

0x34b655…2a6f

6 touches
3 conflicts

0x3e49348b…9445

0x34b655…2a6f

4 touches
1 conflict

0x4786839b…c29a

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 0x482471adbb…39122f

← previous block·next block →recent activity