← previous blocknext block →recent activity

Analyzing

Block #99,248,030

22 transactions · 22 stateful · 2026-08-26 05:41:14 UTC

Parallelism

73/100

Blocked

36%

Avg conflicts / tx

0.59

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #99,248,030  ·  22 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x62910921…3016

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x2e66d2fb…d2e2

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x3711ff0c…12e5

0x34b655…2a6f

4 touches
1 conflict

0x59c86592…f538

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

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 0x629109215a…273016

← previous block·next block →recent activity