← previous blocknext block →recent activity

Analyzing

Block #97,611,428

21 transactions · 19 stateful · 2026-08-20 11:18:44 UTC

Parallelism

76/100

Blocked

42%

Avg conflicts / tx

0.81

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,611,428  ·  21 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x87a380d9…2d04

0x34b655…2a6f

10 touches
10 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x3b3a5945…10d0

0x34b655…2a6f

4 touches
1 conflict

0x3d93ad2c…e747

0x34b655…2a6f

4 touches
1 conflict

0xc3baa205…f26e

0x34b655…2a6f

4 touches
1 conflict

0x5fc4192a…fe67

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

10 conflicts on slot 0x87a380d9ab…192d04

← previous block·next block →recent activity