← previous blocknext block →recent activity

Analyzing

Block #99,250,230

21 transactions · 18 stateful · 2026-08-26 05:52:18 UTC

Parallelism

81/100

Blocked

39%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,250,230  ·  21 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

0xab60dc09…85e4

0x34b655…2a6f

6 touches
3 conflicts

0xfee6bea4…80eb

0x40c49f…2af0

4 touches
1 conflict

0x41469894…5990

0x34b655…2a6f

4 touches
1 conflict

0x9d2b1b5c…55f2

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0xf2dc7074…4491

0x34b655…2a6f

4 touches
1 conflict

0xf95fa02e…ad51

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 0xab60dc0972…4c85e4

← previous block·next block →recent activity