← previous blocknext block →recent activity

Analyzing

Block #95,646,686

21 transactions · 19 stateful · 2026-08-13 13:46:09 UTC

Parallelism

81/100

Blocked

32%

Avg conflicts / tx

0.43

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,646,686  ·  21 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

0x81a169fb…d227

0x34b655…2a6f

6 touches
3 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

6 touches
3 conflicts

0x03b16972…8f62

0x34b655…2a6f

4 touches
1 conflict

0x0f82dba2…24d6

0x34b655…2a6f

4 touches
1 conflict

0x1c106a56…de20

0x34b655…2a6f

4 touches
1 conflict

0x1d082421…ff2d

0x34b655…2a6f

4 touches
1 conflict

0x286711a5…b3bf

0x34b655…2a6f

4 touches
1 conflict

0x2ea9b642…13ed

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 0x81a169fb15…f9d227

← previous block·next block →recent activity