← previous blocknext block →recent activity

Analyzing

Block #97,570,737

20 transactions · 18 stateful · 2026-08-20 07:52:42 UTC

Parallelism

70/100

Blocked

33%

Avg conflicts / tx

0.85

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #97,570,737  ·  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

0x0099420d…37b4

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x21ca7579…1a1e

0x34b655…2a6f

6 touches
3 conflicts

0xad9007e9…2a92

0x34b655…2a6f

6 touches
3 conflicts

0x7d6b9af1…9a38

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0007

0xc1570a…c91b

4 touches
1 conflict

0x0214b385…f83d

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 0x0099420dea…e337b4

← previous block·next block →recent activity