← previous blocknext block →recent activity

Analyzing

Block #86,629,019

23 transactions · 21 stateful · 2026-07-09 13:07:32 UTC

Parallelism

87/100

Blocked

24%

Avg conflicts / tx

0.26

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,629,019  ·  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

0x08a5c23d…ca1e

0x34b655…2a6f

4 touches
1 conflict

0x123ecd5a…d7cf

0x34b655…2a6f

4 touches
1 conflict

0x22bc4ea4…5c8a

0x34b655…2a6f

4 touches
1 conflict

0x22e0cc1d…ad0d

0x34b655…2a6f

4 touches
1 conflict

0x321eac33…6aca

0x34b655…2a6f

4 touches
1 conflict

0x3483ab79…8ed3

0x34b655…2a6f

4 touches
1 conflict

0x636fd21a…9978

0x34b655…2a6f

4 touches
1 conflict

0x63c900f4…2600

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

1 conflict on slot 0x08a5c23d3c…ecca1e

← previous block·next block →recent activity