← previous blocknext block →recent activity

Analyzing

Block #97,493,899

24 transactions · 24 stateful · 2026-08-20 01:24:28 UTC

Parallelism

79/100

Blocked

29%

Avg conflicts / tx

0.33

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,493,899  ·  24 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0007

0xc1570a…c91b

4 touches
1 conflict

0xb64473b0…0d6f

0xc8689a…ee79

4 touches
1 conflict

0x22e0cc1d…ad04

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xc948dbdc…199a

0x34b655…2a6f

4 touches
1 conflict

0xda1f3e2c…b73d

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

3 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity