← previous blocknext block →recent activity

Analyzing

Block #87,727,670

23 transactions · 18 stateful · 2026-07-14 15:34:25 UTC

Parallelism

87/100

Blocked

39%

Avg conflicts / tx

0.43

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #87,727,670  ·  23 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

0x69a45f39…39aa

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…0001

0xc1ff9f…b0fc

6 touches
3 conflicts

0x6c26d635…1bbf

0x34b655…2a6f

4 touches
1 conflict

0x9375a764…dca1

0x34b655…2a6f

4 touches
1 conflict

0xac2a0273…721b

0x34b655…2a6f

4 touches
1 conflict

0xafb8e71e…9285

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xdfa9b704…9d46

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 0x69a45f39d6…c739aa

← previous block·next block →recent activity