← previous blocknext block →recent activity

Analyzing

Block #95,758,601

17 transactions · 17 stateful · 2026-08-13 23:10:05 UTC

Parallelism

76/100

Blocked

35%

Avg conflicts / tx

0.59

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,758,601  ·  17 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0x8f63f383…6eda

0x34b655…2a6f

6 touches
3 conflicts

0x7f09ba37…2403

0x34b655…2a6f

6 touches
3 conflicts

0x09106a95…1467

0x33176b…e078

4 touches
1 conflict

0x59a54ff4…d21b

0x34b655…2a6f

4 touches
1 conflict

0x5d1ac445…5233

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b77

0x34b655…2a6f

4 touches
1 conflict

0x6d1b72ee…6b78

0x34b655…2a6f

4 touches
1 conflict

0x7dc3c875…76ce

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 0x8f63f383d9…ff6eda

← previous block·next block →recent activity