← previous blocknext block →recent activity

Analyzing

Block #86,741,791

23 transactions · 22 stateful · 2026-07-10 01:41:57 UTC

Parallelism

65/100

Blocked

36%

Avg conflicts / tx

0.74

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #86,741,791  ·  23 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0x7e5ea60a…c4aa

0x34b655…2a6f

8 touches
6 conflicts

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x0733be30…112f

0x34b655…2a6f

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x63ef3eae…b1ea

0x34b655…2a6f

6 touches
3 conflicts

0xbc4e7b49…3d2d

0x34b655…2a6f

6 touches
3 conflicts

0xc53799eb…d928

0x34b655…2a6f

4 touches
1 conflict

0x5f251b96…6054

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

6 conflicts on slot 0x7e5ea60ab2…b0c4aa

← previous block·next block →recent activity