← previous blocknext block →recent activity

Analyzing

Block #98,496,211

21 transactions · 19 stateful · 2026-08-23 13:55:50 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,496,211  ·  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

0xc284529b…9553

0x34b655…2a6f

6 touches
3 conflicts

0x8ff85b19…dde0

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x67a56c8b…f955

0x34b655…2a6f

6 touches
3 conflicts

0x42e5184f…4e8b

0x34b655…2a6f

4 touches
1 conflict

0x7aa5d2c4…d6ef

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 0xc284529b04…e29553

← previous block·next block →recent activity