← previous blocknext block →recent activity

Analyzing

Block #86,220,531

23 transactions · 20 stateful · 2026-07-07 15:36:46 UTC

Parallelism

70/100

Blocked

40%

Avg conflicts / tx

0.96

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,220,531  ·  23 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0xcc58c80b…ff79

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0x248d67c0…e6eb

0x34b655…2a6f

6 touches
3 conflicts

0x34d95d94…3a16

0x34b655…2a6f

6 touches
3 conflicts

0x41be9e75…9773

0x34b655…2a6f

6 touches
3 conflicts

0xbcc5ae85…6ba2

0xa6afd3…d132

6 touches
3 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

6 touches
3 conflicts

0x839c0c71…bada

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

10 conflicts on slot 0xcc58c80b6c…80ff79

← previous block·next block →recent activity