← previous blocknext block →recent activity

Analyzing

Block #97,497,155

24 transactions · 24 stateful · 2026-08-20 01:40:51 UTC

Parallelism

58/100

Blocked

42%

Avg conflicts / tx

1.46

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #97,497,155  ·  24 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x4c693b8f…8edd

0x34b655…2a6f

12 touches
15 conflicts

0xcf80e177…646c

0x34b655…2a6f

10 touches
10 conflicts

0x516e9b35…57e7

0x34b655…2a6f

8 touches
6 conflicts

0x75c84b81…cf28

0x34b655…2a6f

6 touches
3 conflicts

0xb5924647…4cf1

0x34b655…2a6f

6 touches
3 conflicts

0x3fa1fac4…826c

0x34b655…2a6f

6 touches
3 conflicts

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