← previous blocknext block →recent activity

Analyzing

Block #95,369,885

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

Parallelism

84/100

Blocked

39%

Avg conflicts / tx

0.47

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #95,369,885  ·  19 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

0xbde524f4…43bf

0x34b655…2a6f

6 touches
3 conflicts

0xd4893967…d7f3

0x34b655…2a6f

5 touches
3 conflicts

0x52f3d91c…1822

0x34b655…2a6f

4 touches
1 conflict

0x66d5e476…8a1f

0x34b655…2a6f

4 touches
1 conflict

0x7523c6af…ea66

0x34b655…2a6f

4 touches
1 conflict

0x7b41d5cd…00e6

0x34b655…2a6f

4 touches
1 conflict

0x7e5ea60a…c4aa

0x34b655…2a6f

4 touches
1 conflict

0x92385428…6941

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