← previous blocknext block →recent activity

Analyzing

Block #86,540,289

16 transactions · 14 stateful · 2026-07-09 03:12:51 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,540,289  ·  16 txs across 2 waves  ·  depth 2
parallel ↔ serial

wave w0

wave w1

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

0x1e48811e…2e39

0x34b655…2a6f

4 touches
1 conflict

0xaba6578d…bd48

0x34b655…2a6f

4 touches
1 conflict

0xafe3acc8…5c1c

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xdb3937e8…23cb

0x34b655…2a6f

4 touches
1 conflict

0xf8c2f856…9b1b

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

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 0x1e48811ed6…842e39

← previous block·next block →recent activity