← previous blocknext block →recent activity

Analyzing

Block #95,471,906

23 transactions · 19 stateful · 2026-08-12 23:07:02 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.61

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #95,471,906  ·  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

0x4acbdbcf…a8c6

0x34b655…2a6f

8 touches
6 conflicts

0x00000000…003d

0xa6afd3…d132

8 touches
6 conflicts

0x889d5e90…929a

0x2a68ba…90c5

6 touches
3 conflicts

0x1803586e…d149

0xa6afd3…d132

6 touches
3 conflicts

0x3464bbc5…a323

0xa6afd3…d132

6 touches
3 conflicts

0x5778d110…d2e6

0xc8689a…ee79

6 touches
3 conflicts

0xeba56708…8cd7

0x2b46c0…1669

4 touches
1 conflict

0x00ddbbf2…4588

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 0x4acbdbcf7f…d0a8c6

← previous block·next block →recent activity