← previous blocknext block →recent activity

Analyzing

Block #86,812,335

16 transactions · 14 stateful · 2026-07-10 09:33:06 UTC

Parallelism

88/100

Blocked

14%

Avg conflicts / tx

0.13

Longest chain

2 deep

Execution timeline

did this block parallelize well?

view

block #86,812,335  ·  16 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

0xb5a3b1be…8122

0x34b655…2a6f

4 touches
1 conflict

0xc824469a…6425

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0x482471ad…122f

0x34b655…2a6f

4 touches
1 conflict

0x83dee4ed…fbad

0x34b655…2a6f

4 touches
1 conflict

0x868b0438…4d17

0x34b655…2a6f

4 touches
1 conflict

0x2d94ecd9…43db

0x34b655…2a6f

4 touches
1 conflict

0x3eede796…d745

0x34b655…2a6f

2 touches
0 conflicts

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 0xb5a3b1be7c…288122

← previous block·next block →recent activity