← previous blocknext block →recent activity

Analyzing

Block #95,542,212

20 transactions · 20 stateful · 2026-08-13 05:00:40 UTC

Parallelism

75/100

Blocked

35%

Avg conflicts / tx

0.75

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,542,212  ·  20 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0x9f64b79f…6722

0x34b655…2a6f

8 touches
6 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x66d5e476…8a1f

0x34b655…2a6f

6 touches
3 conflicts

0x42522e76…2593

0x34b655…2a6f

4 touches
1 conflict

0x4baeeb21…47d7

0x34b655…2a6f

4 touches
1 conflict

0x588380ee…0a5c

0x34b655…2a6f

4 touches
1 conflict

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x850def09…120b

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

6 conflicts on slot 0x9f64b79f42…d06722

← previous block·next block →recent activity