← previous blocknext block →recent activity

Analyzing

Block #97,361,226

18 transactions · 17 stateful · 2026-08-19 13:53:05 UTC

Parallelism

72/100

Blocked

41%

Avg conflicts / tx

0.61

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,361,226  ·  18 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

0x74f95963…01a2

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x48b13e5e…3c2a

0x34b655…2a6f

4 touches
1 conflict

0x55b2239f…fec5

0x34b655…2a6f

4 touches
1 conflict

0x96acee69…ef76

0x34b655…2a6f

4 touches
1 conflict

0xa3f095f5…bd87

0x34b655…2a6f

4 touches
1 conflict

0xafd867b7…2b2d

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 0x74f9596374…0201a2

← previous block·next block →recent activity