← previous blocknext block →recent activity

Analyzing

Block #99,481,641

17 transactions · 15 stateful · 2026-08-27 01:17:18 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.65

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,481,641  ·  17 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

0xd6113c0f…0a4b

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x8e17ea21…8be1

0x34b655…2a6f

6 touches
3 conflicts

0xfa09be5a…1e79

0x34b655…2a6f

6 touches
3 conflicts

0x4ee9273e…735f

0xd32edf…ff58

5 touches
3 conflicts

0x310a7246…2dcb

0x34b655…2a6f

4 touches
1 conflict

0x3c2d19c2…51da

0x34b655…2a6f

4 touches
1 conflict

0x8d5fc820…1750

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 0xd6113c0f7f…b30a4b

← previous block·next block →recent activity