← previous blocknext block →recent activity

Analyzing

Block #97,711,496

22 transactions · 22 stateful · 2026-08-20 19:51:26 UTC

Parallelism

77/100

Blocked

36%

Avg conflicts / tx

0.64

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,711,496  ·  22 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

0x9db64d13…fb98

0x34b655…2a6f

6 touches
3 conflicts

0xc2e8bece…67d9

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x422d5490…52d9

0x34b655…2a6f

4 touches
1 conflict

0x8f80e25f…fbfc

0xa6afd3…d132

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x01737532…9b12

0x34b655…2a6f

4 touches
1 conflict

0xc08f0dac…68aa

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

3 conflicts on slot 0x9db64d13f5…6efb98

← previous block·next block →recent activity