← previous blocknext block →recent activity

Analyzing

Block #95,074,472

13 transactions · 13 stateful · 2026-08-11 13:34:23 UTC

Parallelism

69/100

Blocked

38%

Avg conflicts / tx

0.77

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,074,472  ·  13 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

0xf3d10975…0d07

0x34b655…2a6f

6 touches
3 conflicts

0x7c93b38a…9e69

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0x6b47245e…a342

0x34b655…2a6f

4 touches
1 conflict

0x78b52df8…344b

0x34b655…2a6f

4 touches
1 conflict

0x7b42f6a7…f49c

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 0xf3d10975b0…050d07

← previous block·next block →recent activity