← previous blocknext block →recent activity

Analyzing

Block #85,166,535

19 transactions · 16 stateful · 2026-07-02 18:31:35 UTC

Parallelism

74/100

Blocked

56%

Avg conflicts / tx

0.74

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,166,535  ·  19 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

0x2c506459…5351

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x3230277c…ef39

0xc8689a…ee79

6 touches
3 conflicts

0x3923cd2c…e6d3

0x34b655…2a6f

6 touches
3 conflicts

0xd29e547b…a1dd

0x34b655…2a6f

6 touches
3 conflicts

0x00000000…002a

0x1b6862…e19c

4 touches
1 conflict

0x65bd5770…5ecc

0x1b6862…e19c

4 touches
1 conflict

0xd9f18d9a…141d

0x1b6862…e19c

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 0x2c5064597d…ee5351

← previous block·next block →recent activity