← previous blocknext block →recent activity

Analyzing

Block #99,935,069

25 transactions · 24 stateful · 2026-08-28 15:33:15 UTC

Parallelism

84/100

Blocked

25%

Avg conflicts / tx

0.36

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,935,069  ·  25 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

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x82aff872…3f28

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x0d03bddb…6658

0x34b655…2a6f

4 touches
1 conflict

0x7e06d07b…36af

0x34b655…2a6f

4 touches
1 conflict

0x9ff4ca89…6115

0x34b655…2a6f

4 touches
1 conflict

0xb5c7c6aa…fdba

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