← previous blocknext block →recent activity

Analyzing

Block #97,355,825

16 transactions · 16 stateful · 2026-08-19 13:25:09 UTC

Parallelism

75/100

Blocked

44%

Avg conflicts / tx

0.75

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,355,825  ·  16 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

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0x588380ee…0a5c

0x34b655…2a6f

6 touches
3 conflicts

0x74a2c581…c965

0x34b655…2a6f

6 touches
3 conflicts

0x731f2745…9370

0xa6afd3…d132

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0xe1d743ba…11c9

0x34b655…2a6f

4 touches
1 conflict

0xf18906a6…d2e3

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

6 conflicts on slot 0xb3fb9fb561…7664db

← previous block·next block →recent activity