← previous blocknext block →recent activity

Analyzing

Block #97,989,410

19 transactions · 17 stateful · 2026-08-21 19:24:24 UTC

Parallelism

63/100

Blocked

47%

Avg conflicts / tx

1

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #97,989,410  ·  19 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

0x92385428…6941

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

10 touches
10 conflicts

0x886db264…846e

0x34b655…2a6f

8 touches
6 conflicts

0x7f6581c2…7ade

0x34b655…2a6f

7 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x87bcbf33…a977

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 0x92385428ad…dc6941

← previous block·next block →recent activity