← previous blocknext block →recent activity

Analyzing

Block #97,397,449

23 transactions · 22 stateful · 2026-08-19 17:17:14 UTC

Parallelism

83/100

Blocked

32%

Avg conflicts / tx

0.35

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,397,449  ·  23 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x984e4d8c…9912

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0007

0xc1570a…c91b

4 touches
1 conflict

0x6bc293e9…556e

0x34b655…2a6f

4 touches
1 conflict

0x71e3d7a7…e367

0x34b655…2a6f

4 touches
1 conflict

0xaab9957c…a4bf

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0x984e4d8c3b…799912

← previous block·next block →recent activity