← previous blocknext block →recent activity

Analyzing

Block #95,205,739

20 transactions · 20 stateful · 2026-08-12 00:34:40 UTC

Parallelism

80/100

Blocked

40%

Avg conflicts / tx

0.7

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,205,739  ·  20 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

0xd66696e0…0842

0x34b655…2a6f

8 touches
6 conflicts

0x9f90a525…ef13

0x34b655…2a6f

6 touches
3 conflicts

0x524f0872…0d12

0x34b655…2a6f

6 touches
3 conflicts

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x7deb183c…0858

0x34b655…2a6f

5 touches
3 conflicts

0xc782ec05…5bb2

0xa6afd3…d132

4 touches
1 conflict

0x217bd767…b79e

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 0xd66696e0dc…230842

← previous block·next block →recent activity