← previous blocknext block →recent activity

Analyzing

Block #99,668,828

16 transactions · 16 stateful · 2026-08-27 17:06:46 UTC

Parallelism

69/100

Blocked

38%

Avg conflicts / tx

0.69

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #99,668,828  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x57e5abc1…286f

0x34b655…2a6f

6 touches
3 conflicts

0x89eaf36a…4e48

0x34b655…2a6f

6 touches
3 conflicts

0x290abc80…f606

0x34b655…2a6f

4 touches
1 conflict

0x6713b018…05f3

0x34b655…2a6f

4 touches
1 conflict

0x6bc08e00…3bf8

0x34b655…2a6f

4 touches
1 conflict

0x6df1d50f…8a92

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 0x482471adbb…39122f

← previous block·next block →recent activity