← previous blocknext block →recent activity

Analyzing

Block #95,580,627

23 transactions · 23 stateful · 2026-08-13 08:13:52 UTC

Parallelism

83/100

Blocked

35%

Avg conflicts / tx

0.57

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,580,627  ·  23 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

8 touches
6 conflicts

0x95c47f03…f1bb

0x34b655…2a6f

6 touches
3 conflicts

0xb371802a…310c

0x34b655…2a6f

6 touches
3 conflicts

0x0a57a2b8…3cdd

0x34b655…2a6f

6 touches
3 conflicts

0xfcbb2fd8…a764

0x34b655…2a6f

5 touches
3 conflicts

0x737acb78…fce8

0x34b655…2a6f

4 touches
1 conflict

0x7d56aa74…a011

0x34b655…2a6f

4 touches
1 conflict

0x8925be8e…4b81

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

← previous block·next block →recent activity