← previous blocknext block →recent activity

Analyzing

Block #98,082,155

22 transactions · 20 stateful · 2026-08-22 03:11:36 UTC

Parallelism

86/100

Blocked

35%

Avg conflicts / tx

0.41

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #98,082,155  ·  22 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

0xd17580f9…ece1

0x754704…b603

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x469dac8d…3411

0x34b655…2a6f

4 touches
1 conflict

0x4be9812b…48a9

0x34b655…2a6f

4 touches
1 conflict

0x79347b24…9fba

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09c

0x34b655…2a6f

4 touches
1 conflict

0xa8c60725…8b65

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

← previous block·next block →recent activity