← previous blocknext block →recent activity

Analyzing

Block #85,134,717

22 transactions · 20 stateful · 2026-07-02 14:59:39 UTC

Parallelism

64/100

Blocked

50%

Avg conflicts / tx

0.82

Longest chain

8 deep

Execution timeline

did this block parallelize well?

view

block #85,134,717  ·  22 txs across 8 waves  ·  depth 8
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

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

0xdeddb1c8…0d40

0x34b655…2a6f

8 touches
6 conflicts

0x229cdc01…286a

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xfde2806f…6d30

0xd32edf…ff58

5 touches
3 conflicts

0x757254ae…d917

0x34b655…2a6f

4 touches
1 conflict

0xe75ce681…ba5f

0x188d58…ea8e

4 touches
1 conflict

0xe75ce681…ba60

0x188d58…ea8e

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