← previous blocknext block →recent activity

Analyzing

Block #97,664,918

27 transactions · 19 stateful · 2026-08-20 15:53:37 UTC

Parallelism

81/100

Blocked

37%

Avg conflicts / tx

0.33

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,664,918  ·  27 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

0xb6b45a7a…88df

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x261cbea7…e35e

0x34b655…2a6f

4 touches
1 conflict

0x04c5c873…dd0a

0xa6afd3…d132

4 touches
1 conflict

0x6c1f806c…7dae

0xa6afd3…d132

4 touches
1 conflict

0x0578e7f1…307b

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

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

3 conflicts on slot 0xb6b45a7adf…5088df

← previous block·next block →recent activity