← previous blocknext block →recent activity

Analyzing

Block #95,716,521

21 transactions · 18 stateful · 2026-08-13 19:38:26 UTC

Parallelism

67/100

Blocked

61%

Avg conflicts / tx

1.19

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #95,716,521  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xb3fb9fb5…64db

0x34b655…2a6f

8 touches
6 conflicts

0x497517b8…6c90

0x34b655…2a6f

8 touches
6 conflicts

0xec7d120d…7084

0x34b655…2a6f

8 touches
6 conflicts

0xc85f42b6…6f23

0x34b655…2a6f

6 touches
3 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 conflicts

0x628359b1…7263

0x34b655…2a6f

4 touches
1 conflict

0x08636046…e60f

0x34b655…2a6f

4 touches
1 conflict

0x2c429f11…0652

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

6 conflicts on slot 0xb3fb9fb561…7664db

← previous block·next block →recent activity