← previous blocknext block →recent activity

Analyzing

Block #97,359,555

17 transactions · 16 stateful · 2026-08-19 13:44:26 UTC

Parallelism

71/100

Blocked

44%

Avg conflicts / tx

1.12

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #97,359,555  ·  17 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

0xc824469a…6425

0x34b655…2a6f

10 touches
10 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0xac2a0273…721b

0x34b655…2a6f

8 touches
6 conflicts

0xa3f095f5…bd87

0x34b655…2a6f

6 touches
3 conflicts

0xbc2413c7…b4c2

0x34b655…2a6f

6 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

6 touches
3 conflicts

0xcb21158b…f18d

0x34b655…2a6f

6 touches
3 conflicts

0xe2e52e46…0894

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 0xc824469a90…af6425

← previous block·next block →recent activity