← previous blocknext block →recent activity

Analyzing

Block #86,513,425

19 transactions · 14 stateful · 2026-07-09 00:13:16 UTC

Parallelism

89/100

Blocked

14%

Avg conflicts / tx

0.11

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,513,425  ·  19 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

0x63c900f4…2600

0x34b655…2a6f

4 touches
1 conflict

0x922c7ebd…6600

0xc8689a…ee79

4 touches
1 conflict

0xfbe9f475…c6f7

0x34b655…2a6f

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0xedcf2991…8551

0x34b655…2a6f

4 touches
1 conflict

0xb48c5e15…60a5

0x34b655…2a6f

4 touches
1 conflict

0xa1144aa9…7f67

0x34b655…2a6f

4 touches
1 conflict

0x7c0bdc54…9dde

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 0x63c900f479…962600

← previous block·next block →recent activity