← previous blocknext block →recent activity

Analyzing

Block #97,991,023

16 transactions · 16 stateful · 2026-08-21 19:32:37 UTC

Parallelism

69/100

Blocked

44%

Avg conflicts / tx

0.94

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,991,023  ·  16 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x01ace6c4…a4e3

0x34b655…2a6f

4 touches
1 conflict

0x0dfd8251…e5b2

0x34b655…2a6f

4 touches
1 conflict

0x3e49348b…9445

0x34b655…2a6f

4 touches
1 conflict

0x3fff7ccd…5a48

0x34b655…2a6f

4 touches
1 conflict

0x45de70d9…e1dc

0x34b655…2a6f

4 touches
1 conflict

0x4ffb5637…e5c4

0x34b655…2a6f

4 touches
1 conflict

0x5e0b8bbe…377b

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

10 conflicts on slot 0xca841faae5…71486a

← previous block·next block →recent activity