← previous blocknext block →recent activity

Analyzing

Block #95,201,325

19 transactions · 19 stateful · 2026-08-12 00:12:28 UTC

Parallelism

79/100

Blocked

37%

Avg conflicts / tx

0.58

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,201,325  ·  19 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

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x424934c8…f2f1

0x34b655…2a6f

6 touches
3 conflicts

0xca841faa…486a

0x34b655…2a6f

6 touches
3 conflicts

0x2655625d…b058

0x34b655…2a6f

4 touches
1 conflict

0x2c602697…299d

0x34b655…2a6f

4 touches
1 conflict

0xfa70f6bb…ea94

0xd18b7e…414b

4 touches
1 conflict

0x000bde1a…e123

0x34b655…2a6f

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

3 conflicts on slot 0xac2a02739b…81721b

← previous block·next block →recent activity