← previous blocknext block →recent activity

Analyzing

Block #95,587,429

27 transactions · 26 stateful · 2026-08-13 08:48:04 UTC

Parallelism

81/100

Blocked

27%

Avg conflicts / tx

0.37

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #95,587,429  ·  27 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xbcbf5d09…8bac

0x34b655…2a6f

6 touches
3 conflicts

0xac2a0273…721b

0x34b655…2a6f

6 touches
3 conflicts

0x04994ed2…9032

0x34b655…2a6f

4 touches
1 conflict

0x10f18761…8e0c

0x34b655…2a6f

4 touches
1 conflict

0x19439a65…eb51

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x5f453c44…fa94

0x34b655…2a6f

4 touches
1 conflict

0x66d5e476…8a1f

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 0xbcbf5d09a8…c68bac

← previous block·next block →recent activity