← previous blocknext block →recent activity

Analyzing

Block #95,084,628

25 transactions · 19 stateful · 2026-08-11 14:25:28 UTC

Parallelism

84/100

Blocked

37%

Avg conflicts / tx

0.4

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,084,628  ·  25 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xb39cb1d8…effa

0x34b655…2a6f

6 touches
3 conflicts

0x38bdc5d3…a632

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x7b67f6cf…0aab

0x34b655…2a6f

4 touches
1 conflict

0xa79ea5bd…f596

0x34b655…2a6f

4 touches
1 conflict

0xb4527790…c282

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0xb39cb1d8c6…28effa

← previous block·next block →recent activity