← previous blocknext block →recent activity

Analyzing

Block #97,517,910

20 transactions · 20 stateful · 2026-08-20 03:25:16 UTC

Parallelism

75/100

Blocked

35%

Avg conflicts / tx

0.55

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,517,910  ·  20 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

8 touches
6 conflicts

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x25ff7717…d4af

0x34b655…2a6f

6 touches
3 conflicts

0x3b5fbc7d…c8fe

0x34b655…2a6f

4 touches
1 conflict

0x54af0a77…1968

0x34b655…2a6f

4 touches
1 conflict

0x705d8def…28b0

0x34b655…2a6f

4 touches
1 conflict

0x8d4c0bb9…ccd3

0x34b655…2a6f

4 touches
1 conflict

0x9fd37234…2731

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