← previous blocknext block →recent activity

Analyzing

Block #97,383,947

31 transactions · 21 stateful · 2026-08-19 15:50:31 UTC

Parallelism

87/100

Blocked

29%

Avg conflicts / tx

0.29

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #97,383,947  ·  31 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x7de57974…f5ba

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0xca841faa…486a

0x34b655…2a6f

4 touches
1 conflict

0x0a884250…b89f

0xd32edf…ff58

3 touches
1 conflict

0xa69697cf…ca67

0x34b655…2a6f

3 touches
1 conflict

0x97b36970…6c2c

0x40c49f…2af0

3 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 0x482471adbb…39122f

← previous block·next block →recent activity