← previous blocknext block →recent activity

Analyzing

Block #98,552,041

21 transactions · 20 stateful · 2026-08-23 18:46:34 UTC

Parallelism

86/100

Blocked

30%

Avg conflicts / tx

0.33

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,552,041  ·  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

0xb51a7ce8…5102

0x34b655…2a6f

6 touches
3 conflicts

0x0b10f1de…fc43

0x34b655…2a6f

4 touches
1 conflict

0x1a2055c7…9054

0x34b655…2a6f

4 touches
1 conflict

0x640c4fb2…044a

0x34b655…2a6f

4 touches
1 conflict

0x68531239…e9a3

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x7ec9cda3…6ddb

0x34b655…2a6f

4 touches
1 conflict

0x84d74093…7808

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 0xb51a7ce8f8…ac5102

← previous block·next block →recent activity