← previous blocknext block →recent activity

Analyzing

Block #95,915,309

14 transactions · 12 stateful · 2026-08-14 12:18:32 UTC

Parallelism

79/100

Blocked

17%

Avg conflicts / tx

0.21

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,915,309  ·  14 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

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0xbcbf5d09…8bac

0x34b655…2a6f

4 touches
1 conflict

0xfb378fb4…bb46

0x34b655…2a6f

4 touches
1 conflict

0x23253ea8…e0a4

0x34b655…2a6f

2 touches
0 conflicts

0x25191452…d2ed

0x34b655…2a6f

2 touches
0 conflicts

0x2d94ecd9…43db

0x34b655…2a6f

2 touches
0 conflicts

0x8d4c0bb9…ccd3

0x34b655…2a6f

2 touches
0 conflicts

0xc0a4133e…6110

0x34b655…2a6f

2 touches
0 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

3 conflicts on slot 0xc824469a90…af6425

← previous block·next block →recent activity