← previous blocknext block →recent activity

Analyzing

Block #95,085,711

16 transactions · 15 stateful · 2026-08-11 14:30:55 UTC

Parallelism

81/100

Blocked

47%

Avg conflicts / tx

0.56

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,085,711  ·  16 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

0x0d2de0f6…e6c6

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xe8e4c015…5718

0x34b655…2a6f

4 touches
1 conflict

0x889d5e90…929a

0x2a68ba…90c5

4 touches
1 conflict

0x07d8b1e8…78c6

0x34b655…2a6f

4 touches
1 conflict

0x0a0cecef…4ed0

0x34b655…2a6f

4 touches
1 conflict

0x19795ad6…4a16

0x34b655…2a6f

4 touches
1 conflict

0x38bdc5d3…a632

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 0x0d2de0f636…8fe6c6

← previous block·next block →recent activity