← previous blocknext block →recent activity

Analyzing

Block #86,659,964

27 transactions · 18 stateful · 2026-07-09 16:35:36 UTC

Parallelism

85/100

Blocked

44%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,659,964  ·  27 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

0xc824469a…6425

0x34b655…2a6f

8 touches
6 conflicts

0x6286219a…0721

0xb1dbf0…c0d3

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x07b979bc…3564

0xb1dbf0…c0d3

6 touches
3 conflicts

0x8a35acfb…d1aa

0xb1dbf0…c0d3

6 touches
3 conflicts

0x8a35acfb…d1ab

0xb1dbf0…c0d3

6 touches
3 conflicts

0x482471ad…122f

0x34b655…2a6f

6 touches
3 conflicts

0x7f61433e…ef60

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 0xc824469a90…af6425

← previous block·next block →recent activity