← previous blocknext block →recent activity

Analyzing

Block #97,519,131

28 transactions · 22 stateful · 2026-08-20 03:31:25 UTC

Parallelism

89/100

Blocked

32%

Avg conflicts / tx

0.32

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #97,519,131  ·  28 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

6 touches
3 conflicts

0x90d81b88…3a34

0x34b655…2a6f

4 touches
1 conflict

0xae982663…7928

0x34b655…2a6f

4 touches
1 conflict

0x655aa1bb…138c

0x40c49f…2af0

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x8ee326b5…3039

0xa6afd3…d132

4 touches
1 conflict

0x9d67cfe8…0db6

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 0x22e0cc1d4a…90ad0d

← previous block·next block →recent activity