← previous blocknext block →recent activity

Analyzing

Block #99,502,659

21 transactions · 20 stateful · 2026-08-27 03:03:07 UTC

Parallelism

81/100

Blocked

35%

Avg conflicts / tx

0.62

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #99,502,659  ·  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

0xca841faa…486a

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

6 touches
3 conflicts

0x92385428…6941

0x34b655…2a6f

6 touches
3 conflicts

0x0d622e34…0000

0x681e90…ae09

4 touches
1 conflict

0x0179e71d…e168

0x34b655…2a6f

4 touches
1 conflict

0x805d08cf…3cfc

0x34b655…2a6f

4 touches
1 conflict

0x9b675cde…5645

0x34b655…2a6f

4 touches
1 conflict

0xabdf81c9…b3b0

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