← previous blocknext block →recent activity

Analyzing

Block #86,080,404

28 transactions · 23 stateful · 2026-07-07 00:01:18 UTC

Parallelism

79/100

Blocked

39%

Avg conflicts / tx

0.89

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #86,080,404  ·  28 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xea02471d…1542

0x34b655…2a6f

10 touches
10 conflicts

0x57f4c459…1bdb

0xd32edf…ff58

9 touches
10 conflicts

0x070a562a…8147

0x34b655…2a6f

6 touches
3 conflicts

0x4d3e58e0…a2d7

0x34b655…2a6f

6 touches
3 conflicts

0x58a05242…188a

0x34b655…2a6f

6 touches
3 conflicts

0x6637e421…af93

0x34b655…2a6f

6 touches
3 conflicts

0x94dabb65…43a3

0x34b655…2a6f

6 touches
3 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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity