← previous blocknext block →recent activity

Analyzing

Block #98,567,761

20 transactions · 20 stateful · 2026-08-23 20:08:46 UTC

Parallelism

70/100

Blocked

35%

Avg conflicts / tx

0.8

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #98,567,761  ·  20 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0x326a02b5…8dad

0x34b655…2a6f

8 touches
6 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0xe9457301…83cd

0x34b655…2a6f

6 touches
3 conflicts

0x67291160…cdf4

0x34b655…2a6f

6 touches
3 conflicts

0x152a2f3e…13f8

0x34b655…2a6f

6 touches
3 conflicts

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 0x326a02b5c5…5c8dad

← previous block·next block →recent activity