← previous blocknext block →recent activity

Analyzing

Block #86,746,950

21 transactions · 14 stateful · 2026-07-10 02:16:26 UTC

Parallelism

90/100

Blocked

14%

Avg conflicts / tx

0.1

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,746,950  ·  21 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

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0xfb0a4eb5…8be3

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09d

0x34b655…2a6f

4 touches
1 conflict

0x793aa64d…b09c

0x34b655…2a6f

4 touches
1 conflict

0x04cf3b3e…bdf7

0xd32edf…ff58

3 touches
1 conflict

0x5591fd1c…db2d

0x34b655…2a6f

3 touches
1 conflict

0xf851c500…1300

0x34b655…2a6f

3 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 0x482471adbb…39122f

← previous block·next block →recent activity