← previous blocknext block →recent activity

Analyzing

Block #86,656,038

22 transactions · 21 stateful · 2026-07-09 16:09:23 UTC

Parallelism

82/100

Blocked

33%

Avg conflicts / tx

0.45

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #86,656,038  ·  22 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

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…000a

0x90c374…be45

6 touches
3 conflicts

0x00000000…000b

0x90c374…be45

6 touches
3 conflicts

0x47d4745e…02bb

0x336ed4…c59c

6 touches
3 conflicts

0x4a870d86…79ef

0x336ed4…c59c

6 touches
3 conflicts

0x8a35acfb…d1aa

0xb1dbf0…c0d3

6 touches
3 conflicts

0x9a291a56…9a9c

0x34b655…2a6f

4 touches
1 conflict

0xa6c4c171…5da8

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

3 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity