← previous blocknext block →recent activity

Analyzing

Block #95,369,969

22 transactions · 22 stateful · 2026-08-12 14:32:36 UTC

Parallelism

82/100

Blocked

32%

Avg conflicts / tx

0.41

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,369,969  ·  22 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

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0x529e53cf…38e4

0xa6afd3…d132

4 touches
1 conflict

0x0672e4a2…8d1f

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xb3fb9fb5…64db

0x34b655…2a6f

4 touches
1 conflict

0xbe9baf16…df37

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

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 0xbde524f475…b143bf

← previous block·next block →recent activity