← previous blocknext block →recent activity

Analyzing

Block #99,811,564

20 transactions · 19 stateful · 2026-08-28 05:10:05 UTC

Parallelism

75/100

Blocked

42%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,811,564  ·  20 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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x15698ac9…2a46

0x34b655…2a6f

4 touches
1 conflict

0x2d2b5c10…fc6d

0x34b655…2a6f

4 touches
1 conflict

0x038b9243…553d

0x34b655…2a6f

4 touches
1 conflict

0x99855f24…1573

0x34b655…2a6f

4 touches
1 conflict

0x08e8f2c9…a11a

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 0xca841faae5…71486a

← previous block·next block →recent activity