← previous blocknext block →recent activity

Analyzing

Block #97,493,933

18 transactions · 17 stateful · 2026-08-20 01:24:38 UTC

Parallelism

78/100

Blocked

41%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,493,933  ·  18 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

0x25d909da…1722

0x34b655…2a6f

8 touches
6 conflicts

0xda1f3e2c…b73d

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0007

0xc1570a…c91b

4 touches
1 conflict

0x588ba065…f516

0x34b655…2a6f

4 touches
1 conflict

0x640e6e56…63cc

0x34b655…2a6f

4 touches
1 conflict

0x9217fe9f…6376

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 0x25d909da6b…231722

← previous block·next block →recent activity