← previous blocknext block →recent activity

Analyzing

Block #97,497,415

24 transactions · 22 stateful · 2026-08-20 01:42:09 UTC

Parallelism

71/100

Blocked

36%

Avg conflicts / tx

0.83

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,497,415  ·  24 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

10 touches
10 conflicts

0x966c58d1…5b44

0x34b655…2a6f

8 touches
6 conflicts

0xcf80e177…646c

0x34b655…2a6f

8 touches
6 conflicts

0x516e9b35…57e7

0x34b655…2a6f

6 touches
3 conflicts

0x00f6a8a7…0e6e

0x34b655…2a6f

6 touches
3 conflicts

0x793aa64d…b09c

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09d

0x34b655…2a6f

4 touches
1 conflict

0x7de57974…f5ba

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

10 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity