← previous blocknext block →recent activity

Analyzing

Block #97,818,475

26 transactions · 25 stateful · 2026-08-21 04:51:34 UTC

Parallelism

65/100

Blocked

48%

Avg conflicts / tx

1.31

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #97,818,475  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x7316dc00…c16a

0x34b655…2a6f

10 touches
10 conflicts

0x32f19ff2…d017

0x34b655…2a6f

6 touches
3 conflicts

0xce928f35…ed50

0x34b655…2a6f

6 touches
3 conflicts

0xbe6d0f1c…20a0

0x34b655…2a6f

6 touches
3 conflicts

0x574628e9…dcc3

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity