← previous blocknext block →recent activity

Analyzing

Block #96,115,667

8 transactions · 7 stateful · 2026-08-15 05:06:31 UTC

Parallelism

63/100

Blocked

29%

Avg conflicts / tx

0.38

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #96,115,667  ·  8 txs across 3 waves  ·  depth 3
parallel ↔ serial

wave w0

wave w1

wave w2

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

0xde08e622…d1ce

0x34b655…2a6f

6 touches
3 conflicts

0x0463db49…5d05

0x34b655…2a6f

4 touches
1 conflict

0x07bb3f5a…617e

0x34b655…2a6f

4 touches
1 conflict

0x08e8f2c9…a11a

0x34b655…2a6f

4 touches
1 conflict

0x0dd3d3cd…7281

0x34b655…2a6f

4 touches
1 conflict

0x36dd003d…96f0

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x4d4389b2…6e07

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

3 conflicts on slot 0xde08e62259…8ed1ce

← previous block·next block →recent activity