← previous blocknext block →recent activity

Analyzing

Block #95,725,993

17 transactions · 16 stateful · 2026-08-13 20:26:05 UTC

Parallelism

82/100

Blocked

44%

Avg conflicts / tx

0.65

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,725,993  ·  17 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

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x0bd95eb4…e562

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xfb709ada…240f

0x34b655…2a6f

4 touches
1 conflict

0x59b05a20…8879

0x065c9d…c394

4 touches
1 conflict

0xbb97db90…4c93

0xc8689a…ee79

4 touches
1 conflict

0x002fed35…79fa

0x2a68ba…90c5

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 0x0a57a2b8cd…773cdd

← previous block·next block →recent activity