← previous blocknext block →recent activity

Analyzing

Block #97,567,141

22 transactions · 18 stateful · 2026-08-20 07:34:28 UTC

Parallelism

77/100

Blocked

44%

Avg conflicts / tx

0.86

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,567,141  ·  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

0x3e1b765a…ae54

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0xd3d35cd8…fe55

0x34b655…2a6f

8 touches
6 conflicts

0x5cfec795…7c0e

0x34b655…2a6f

6 touches
3 conflicts

0xb3fb9fb5…64db

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xb4b5966a…081a

0x34b655…2a6f

4 touches
1 conflict

0xb97c885b…2933

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

6 conflicts on slot 0x3e1b765a31…9cae54

← previous block·next block →recent activity