← previous blocknext block →recent activity

Analyzing

Block #97,605,713

23 transactions · 21 stateful · 2026-08-20 10:49:31 UTC

Parallelism

74/100

Blocked

33%

Avg conflicts / tx

0.87

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #97,605,713  ·  23 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

12 touches
15 conflicts

0x482471ad…122f

0x34b655…2a6f

10 touches
10 conflicts

0x513067d4…87ab

0x34b655…2a6f

6 touches
3 conflicts

0x88724b87…5e65

0x34b655…2a6f

6 touches
3 conflicts

0x17f192de…765e

0x34b655…2a6f

4 touches
1 conflict

0x2e5cdd04…22ab

0x34b655…2a6f

4 touches
1 conflict

0xcc9d4fca…ecbf

0x34b655…2a6f

4 touches
1 conflict

0x7aad02c6…b979

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

15 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity