← previous blocknext block →recent activity

Analyzing

Block #98,531,463

18 transactions · 18 stateful · 2026-08-23 16:59:23 UTC

Parallelism

83/100

Blocked

39%

Avg conflicts / tx

0.44

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,531,463  ·  18 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

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x7aad02c6…b979

0x34b655…2a6f

6 touches
3 conflicts

0x0e18d182…0425

0x34b655…2a6f

4 touches
1 conflict

0x1f24937e…aeab

0x34b655…2a6f

4 touches
1 conflict

0x215a6da4…0e86

0x34b655…2a6f

4 touches
1 conflict

0x36a76bd2…1fb0

0x34b655…2a6f

4 touches
1 conflict

0x5d9698ff…d8f9

0x34b655…2a6f

4 touches
1 conflict

0x676019e6…87fc

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 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity