← previous blocknext block →recent activity

Analyzing

Block #97,606,208

20 transactions · 20 stateful · 2026-08-20 10:52:05 UTC

Parallelism

60/100

Blocked

50%

Avg conflicts / tx

1.45

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #97,606,208  ·  20 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x482471ad…122f

0x34b655…2a6f

14 touches
21 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xef76b86f…943e

0x34b655…2a6f

10 touches
10 conflicts

0xef5959a3…2a2f

0x34b655…2a6f

8 touches
6 conflicts

0x2e5cdd04…22ab

0x34b655…2a6f

8 touches
6 conflicts

0xbf56d746…c858

0x34b655…2a6f

6 touches
3 conflicts

0x6183ee9a…21b1

0x34b655…2a6f

6 touches
3 conflicts

0x9ff4ca89…6115

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

21 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity