← previous blocknext block →recent activity

Analyzing

Block #96,838,846

19 transactions · 15 stateful · 2026-08-17 17:44:10 UTC

Parallelism

58/100

Blocked

67%

Avg conflicts / tx

1.32

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #96,838,846  ·  19 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x482471ad…122f

0x34b655…2a6f

12 touches
15 conflicts

0xc824469a…6425

0x34b655…2a6f

12 touches
15 conflicts

0x54a7b790…c2c6

0x34b655…2a6f

10 touches
10 conflicts

0xe6e6f436…ddc0

0x34b655…2a6f

8 touches
6 conflicts

0x96fed898…e5ba

0x34b655…2a6f

8 touches
6 conflicts

0x70986451…c6bd

0x34b655…2a6f

6 touches
3 conflicts

0x04994ed2…9032

0x34b655…2a6f

6 touches
3 conflicts

0x948836ff…59ab

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

15 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity