← previous blocknext block →recent activity

Analyzing

Block #97,656,179

25 transactions · 17 stateful · 2026-08-20 15:08:12 UTC

Parallelism

80/100

Blocked

41%

Avg conflicts / tx

0.32

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,656,179  ·  25 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

6 touches
3 conflicts

0x06d9cabd…bd55

0xa6afd3…d132

4 touches
1 conflict

0x00000000…0002

0x103de0…bb55

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x04a566e1…26f3

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xe5bb3628…e5f1

0x34b655…2a6f

4 touches
1 conflict

0x9a555477…19a8

0x754704…b603

2 touches
0 conflicts

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 0xca841faae5…71486a

← previous block·next block →recent activity