← previous blocknext block →recent activity

Analyzing

Block #97,553,351

20 transactions · 17 stateful · 2026-08-20 06:24:04 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,553,351  ·  20 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

0xbac2713d…167c

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

4 touches
1 conflict

0xc53799eb…d928

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd6f857b1…bae3

0x34b655…2a6f

4 touches
1 conflict

0xe0233c89…4b1f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x00000000…0007

0xc1570a…c91b

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 0xbac2713db7…e7167c

← previous block·next block →recent activity