← previous blocknext block →recent activity

Analyzing

Block #95,206,797

14 transactions · 11 stateful · 2026-08-12 00:39:59 UTC

Parallelism

86/100

Blocked

36%

Avg conflicts / tx

0.29

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #95,206,797  ·  14 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0xec3327a0…dd6e

0x34b655…2a6f

4 touches
1 conflict

0x763104af…f44e

0x34b655…2a6f

4 touches
1 conflict

0x845ec8b0…c1af

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xac2a3901…aca4

0x34b655…2a6f

4 touches
1 conflict

0xbc66586e…20fe

0x34b655…2a6f

4 touches
1 conflict

0xbe9baf16…df37

0x34b655…2a6f

4 touches
1 conflict

0x80afd9d9…57cf

0x065c9d…c394

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

1 conflict on slot 0xec3327a09b…41dd6e

← previous block·next block →recent activity