← previous blocknext block →recent activity

Analyzing

Block #98,261,150

20 transactions · 19 stateful · 2026-08-22 18:12:51 UTC

Parallelism

80/100

Blocked

32%

Avg conflicts / tx

0.5

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #98,261,150  ·  20 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

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xb3037bed…6b7c

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xc45e4fb5…7cc3

0xa6afd3…d132

4 touches
1 conflict

0x20563e16…2a84

0x34b655…2a6f

4 touches
1 conflict

0x326a02b5…8dad

0x34b655…2a6f

4 touches
1 conflict

0x62910921…3016

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 0xac2a02739b…81721b

← previous block·next block →recent activity