← previous blocknext block →recent activity

Analyzing

Block #97,562,781

23 transactions · 21 stateful · 2026-08-20 07:12:17 UTC

Parallelism

74/100

Blocked

38%

Avg conflicts / tx

0.52

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #97,562,781  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

8 touches
6 conflicts

0x26bae314…6822

0x34b655…2a6f

4 touches
1 conflict

0x2d7ea048…d78e

0x34b655…2a6f

4 touches
1 conflict

0x37ed7ce3…537f

0x34b655…2a6f

4 touches
1 conflict

0x3a2a8323…3f40

0x34b655…2a6f

4 touches
1 conflict

0x3c6fca6a…6ffd

0x34b655…2a6f

4 touches
1 conflict

0x4267a231…9d29

0x34b655…2a6f

4 touches
1 conflict

0x4327afd2…1b3a

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 0xca841faae5…71486a

← previous block·next block →recent activity