← previous blocknext block →recent activity

Analyzing

Block #86,808,615

16 transactions · 15 stateful · 2026-07-10 09:08:14 UTC

Parallelism

88/100

Blocked

13%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,808,615  ·  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

0xbb277c58…e388

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xebeee24a…ed8d

0x34b655…2a6f

4 touches
1 conflict

0x0ae9d2df…f787

0x34b655…2a6f

4 touches
1 conflict

0x3eede796…d745

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x00000000…003d

0x851145…3f07

4 touches
1 conflict

0xb8644937…ed09

0x851145…3f07

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 0xbb277c5800…bce388

← previous block·next block →recent activity