← previous blocknext block →recent activity

Analyzing

Block #96,609,529

23 transactions · 17 stateful · 2026-08-16 22:30:48 UTC

Parallelism

57/100

Blocked

65%

Avg conflicts / tx

1.52

Longest chain

10 deep

Execution timeline

did this block parallelize well?

view

block #96,609,529  ·  23 txs across 10 waves  ·  depth 10
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

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

0x2d651956…12e8

0x34b655…2a6f

10 touches
10 conflicts

0xca841faa…486a

0x34b655…2a6f

10 touches
10 conflicts

0x8a5ced1c…3b29

0x34b655…2a6f

8 touches
6 conflicts

0x482471ad…122f

0x34b655…2a6f

8 touches
6 conflicts

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

8 touches
6 conflicts

0x02991b41…19e6

0x34b655…2a6f

8 touches
6 conflicts

0xb37c6e40…1504

0x34b655…2a6f

6 touches
3 conflicts

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 0x2d65195682…4112e8

← previous block·next block →recent activity