← previous blocknext block →recent activity

Analyzing

Block #99,450,235

25 transactions · 21 stateful · 2026-08-26 22:39:10 UTC

Parallelism

68/100

Blocked

43%

Avg conflicts / tx

0.76

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #99,450,235  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x70d81211…f49f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x743d78ae…1848

0x34b655…2a6f

8 touches
6 conflicts

0xbec70249…cff7

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x5b09bf44…5907

0xa6afd3…d132

4 touches
1 conflict

0x482471ad…122f

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 0x70d812119d…c1f49f

← previous block·next block →recent activity