← previous blocknext block →recent activity

Analyzing

Block #97,565,695

20 transactions · 16 stateful · 2026-08-20 07:27:08 UTC

Parallelism

80/100

Blocked

44%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,565,695  ·  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

0x8d989c17…e984

0x34b655…2a6f

6 touches
3 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x6a2ca7be…18a8

0x34b655…2a6f

4 touches
1 conflict

0x721e47d3…d530

0x34b655…2a6f

4 touches
1 conflict

0x75186f80…3615

0x34b655…2a6f

4 touches
1 conflict

0x9d6aeefb…baba

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 0x8d989c177f…b7e984

← previous block·next block →recent activity