← previous blocknext block →recent activity

Analyzing

Block #95,530,894

13 transactions · 11 stateful · 2026-08-13 04:03:43 UTC

Parallelism

85/100

Blocked

27%

Avg conflicts / tx

0.23

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #95,530,894  ·  13 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

0x7726bf58…6524

0x34b655…2a6f

4 touches
1 conflict

0x83da2486…8024

0x34b655…2a6f

4 touches
1 conflict

0x8cd684d0…c3cb

0x34b655…2a6f

4 touches
1 conflict

0x8eb21bd9…aa8b

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xa1087a5c…66c4

0x754704…b603

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 0x7726bf584f…046524

← previous block·next block →recent activity