← previous blocknext block →recent activity

Analyzing

Block #86,215,656

22 transactions · 18 stateful · 2026-07-07 15:04:13 UTC

Parallelism

73/100

Blocked

39%

Avg conflicts / tx

0.64

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

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

10 touches
10 conflicts

0xec0e0220…cb90

0x34b655…2a6f

4 touches
1 conflict

0x442e26a3…e968

0x34b655…2a6f

4 touches
1 conflict

0x4bfdcd51…9b58

0x34b655…2a6f

4 touches
1 conflict

0x4ec8d1b4…4e6e

0x34b655…2a6f

4 touches
1 conflict

0x4ec9ff52…e6f7

0x34b655…2a6f

4 touches
1 conflict

0x4f58b18a…ecc1

0x34b655…2a6f

4 touches
1 conflict

0xa1980c71…f097

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

10 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity