← previous blocknext block →recent activity

Analyzing

Block #97,477,890

25 transactions · 24 stateful · 2026-08-20 00:03:56 UTC

Parallelism

68/100

Blocked

50%

Avg conflicts / tx

1.44

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #97,477,890  ·  25 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0x889d5e90…929a

0x2a68ba…90c5

10 touches
10 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x8b8c3b8a…9b6a

0x2b46c0…1669

4 touches
1 conflict

0xad3ef711…4f2b

0x2b46c0…1669

4 touches
1 conflict

0xb8fccd1b…b5f2

0x2b46c0…1669

4 touches
1 conflict

0xe2263bea…6a9d

0x2b46c0…1669

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

21 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity