← previous blocknext block →recent activity

Analyzing

Block #86,928,740

24 transactions · 20 stateful · 2026-07-10 22:31:29 UTC

Parallelism

88/100

Blocked

30%

Avg conflicts / tx

0.29

Longest chain

3 deep

Execution timeline

did this block parallelize well?

view

block #86,928,740  ·  24 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

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x1741dbc0…73a7

0x34b655…2a6f

4 touches
1 conflict

0x1ba5d36c…9336

0x34b655…2a6f

4 touches
1 conflict

0x33bd5ec4…af53

0xa6afd3…d132

4 touches
1 conflict

0x13a54fa2…5ae3

0x2a68ba…90c5

4 touches
1 conflict

0x7012fd2e…ae67

0x34b655…2a6f

4 touches
1 conflict

0x7012fd2e…ae68

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

3 conflicts on slot 0x482471adbb…39122f

← previous block·next block →recent activity