← previous blocknext block →recent activity

Analyzing

Block #95,723,006

18 transactions · 18 stateful · 2026-08-13 20:11:04 UTC

Parallelism

56/100

Blocked

67%

Avg conflicts / tx

1.89

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #95,723,006  ·  18 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x482471ad…122f

0x34b655…2a6f

16 touches
28 conflicts

0xc824469a…6425

0x34b655…2a6f

16 touches
28 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x3cf50d44…961b

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x81143765…a922

0x34b655…2a6f

6 touches
3 conflicts

0x361c1b83…94da

0x34b655…2a6f

5 touches
3 conflicts

0x705ab4ae…0162

0x34b655…2a6f

5 touches
3 conflicts

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

28 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity