← previous blocknext block →recent activity

Analyzing

Block #86,495,582

17 transactions · 17 stateful · 2026-07-08 22:14:18 UTC

Parallelism

71/100

Blocked

47%

Avg conflicts / tx

0.76

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #86,495,582  ·  17 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

8 touches
6 conflicts

0x94ba9c4a…41d8

0x34b655…2a6f

6 touches
3 conflicts

0x2b5101ac…090b

0x34b655…2a6f

6 touches
3 conflicts

0xcbd23469…a4df

0x34b655…2a6f

6 touches
3 conflicts

0x11560115…bfc2

0x34b655…2a6f

6 touches
3 conflicts

0x8494fdcd…d438

0xd32edf…ff58

5 touches
3 conflicts

0x5f34fd08…aeb3

0x34b655…2a6f

4 touches
1 conflict

0x62e20208…be65

0x0555e3…2b9c

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 0xd98b3c102b…ca67b8

← previous block·next block →recent activity