← previous blocknext block →recent activity

Analyzing

Block #96,708,443

29 transactions · 22 stateful · 2026-08-17 06:48:16 UTC

Parallelism

72/100

Blocked

55%

Avg conflicts / tx

1.1

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #96,708,443  ·  29 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

0xb1b58b33…874f

0x34b655…2a6f

14 touches
21 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0xa1ff0729…0146

0xa6afd3…d132

8 touches
6 conflicts

0x10d80fee…dbda

0x2b46c0…1669

6 touches
3 conflicts

0x40970e69…da50

0x2b46c0…1669

6 touches
3 conflicts

0x8cf3d245…1d0d

0x2b46c0…1669

6 touches
3 conflicts

0xb05cd4f5…73d0

0x2b46c0…1669

6 touches
3 conflicts

0xdb067026…9eb8

0x2b46c0…1669

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

21 conflicts on slot 0xb1b58b3385…e4874f

← previous block·next block →recent activity