← previous blocknext block →recent activity

Analyzing

Block #97,466,728

23 transactions · 20 stateful · 2026-08-19 23:07:32 UTC

Parallelism

78/100

Blocked

35%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,466,728  ·  23 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

0x5cfec795…7c0e

0x34b655…2a6f

6 touches
3 conflicts

0x2dcc0868…26bf

0x34b655…2a6f

6 touches
3 conflicts

0xec7d120d…7084

0x34b655…2a6f

4 touches
1 conflict

0x20c71c23…d507

0x34b655…2a6f

4 touches
1 conflict

0x25d909da…1722

0x34b655…2a6f

4 touches
1 conflict

0x59dccbd8…2bf6

0x34b655…2a6f

4 touches
1 conflict

0x5b26e38f…3654

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