← previous blocknext block →recent activity

Analyzing

Block #86,447,962

18 transactions · 15 stateful · 2026-07-08 16:55:48 UTC

Parallelism

78/100

Blocked

53%

Avg conflicts / tx

0.72

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,447,962  ·  18 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

0x08fcf623…3513

0x34b655…2a6f

6 touches
3 conflicts

0xea02471d…1542

0x34b655…2a6f

6 touches
3 conflicts

0xee4fe1f7…3ead

0x34b655…2a6f

6 touches
3 conflicts

0xda2ee2e7…968a

0x34b655…2a6f

6 touches
3 conflicts

0x0ab54c30…b88e

0x34b655…2a6f

6 touches
3 conflicts

0x9ae859db…2d84

0x34b655…2a6f

6 touches
3 conflicts

0xa3fd4779…1172

0xd32edf…ff58

5 touches
3 conflicts

0xb3572c95…9c4a

0x2a68ba…90c5

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

3 conflicts on slot 0x08fcf62325…603513

← previous block·next block →recent activity