← previous blocknext block →recent activity

Analyzing

Block #97,477,371

26 transactions · 26 stateful · 2026-08-20 00:01:19 UTC

Parallelism

88/100

Blocked

23%

Avg conflicts / tx

0.35

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #97,477,371  ·  26 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

0xe5bb3628…e5f1

0x34b655…2a6f

6 touches
3 conflicts

0x015a51cb…b7b7

0x34b655…2a6f

4 touches
1 conflict

0x076e4b80…4d01

0x34b655…2a6f

4 touches
1 conflict

0x077d58c3…8ed7

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0xbdf92388…94c5

0x40c49f…2af0

4 touches
1 conflict

0x61210edf…0f79

0x40c49f…2af0

4 touches
1 conflict

0x655aa1bb…138c

0x40c49f…2af0

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 0xe5bb3628b5…71e5f1

← previous block·next block →recent activity