← previous blocknext block →recent activity

Analyzing

Block #99,115,795

14 transactions · 14 stateful · 2026-08-25 18:35:50 UTC

Parallelism

79/100

Blocked

50%

Avg conflicts / tx

0.71

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #99,115,795  ·  14 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0xf984d8ab…6e4f

0x34b655…2a6f

4 touches
1 conflict

0xa1731f0f…1f9d

0x34b655…2a6f

4 touches
1 conflict

0xac042d54…6d09

0x34b655…2a6f

4 touches
1 conflict

0xb5cddf91…0abf

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

← previous block·next block →recent activity