← previous blocknext block →recent activity

Analyzing

Block #97,361,200

22 transactions · 21 stateful · 2026-08-19 13:52:57 UTC

Parallelism

64/100

Blocked

38%

Avg conflicts / tx

1.64

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #97,361,200  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x482471ad…122f

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0xfb31d278…9107

0x34b655…2a6f

6 touches
3 conflicts

0x56b75a1a…340c

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0xdb30a641…a0e9

0x34b655…2a6f

6 touches
3 conflicts

0xe2e52e46…0894

0x34b655…2a6f

6 touches
3 conflicts

0xea7754dd…b1b9

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

28 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity