← previous blocknext block →recent activity

Analyzing

Block #97,497,225

22 transactions · 22 stateful · 2026-08-20 01:41:12 UTC

Parallelism

86/100

Blocked

32%

Avg conflicts / tx

0.45

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #97,497,225  ·  22 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

0x886f7fe6…8b7a

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0x40c49f…2af0

4 touches
1 conflict

0x5fde4971…aac9

0x34b655…2a6f

4 touches
1 conflict

0x674688ac…f3e3

0x34b655…2a6f

4 touches
1 conflict

0x728f999a…832f

0x34b655…2a6f

4 touches
1 conflict

0xa21e8abe…a7f1

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

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 0x886f7fe654…c88b7a

← previous block·next block →recent activity