← previous blocknext block →recent activity

Analyzing

Block #86,057,672

18 transactions · 16 stateful · 2026-07-06 21:29:43 UTC

Parallelism

89/100

Blocked

13%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,057,672  ·  18 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

0x76ed8777…1e5f

0x34b655…2a6f

4 touches
1 conflict

0x91ff239c…e07b

0x34b655…2a6f

4 touches
1 conflict

0xa6adf284…c228

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x0dbfce38…f11a

0x34b655…2a6f

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0xd6d040d9…9ae3

0x34b655…2a6f

4 touches
1 conflict

0xec0e0220…cb90

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 0x76ed8777f7…0c1e5f

← previous block·next block →recent activity