← previous blocknext block →recent activity

Analyzing

Block #98,745,649

21 transactions · 17 stateful · 2026-08-24 11:26:39 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,745,649  ·  21 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x51fc8795…1266

0x34b655…2a6f

4 touches
1 conflict

0x5cfbeb21…92b1

0x34b655…2a6f

4 touches
1 conflict

0x306f4f92…a410

0x8964d7…10f8

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x306f4f92…a40d

0x8964d7…10f8

4 touches
1 conflict

0x306f4f92…a40e

0x8964d7…10f8

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 0xc824469a90…af6425

← previous block·next block →recent activity