← previous blocknext block →recent activity

Analyzing

Block #96,557,527

24 transactions · 20 stateful · 2026-08-16 18:09:14 UTC

Parallelism

63/100

Blocked

60%

Avg conflicts / tx

2.08

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #96,557,527  ·  24 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0x1e04ad1e…c417

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

14 touches
21 conflicts

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0x29c1a140…099f

0x34b655…2a6f

12 touches
15 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

10 touches
10 conflicts

0x9fd372a1…a959

0x34b655…2a6f

10 touches
10 conflicts

0xe2e38d6d…b2db

0x34b655…2a6f

8 touches
6 conflicts

0xca841faa…486a

0x34b655…2a6f

8 touches
6 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

28 conflicts on slot 0x1e04ad1e2b…3cc417

← previous block·next block →recent activity