← previous blocknext block →recent activity

Analyzing

Block #85,179,836

20 transactions · 18 stateful · 2026-07-02 20:00:10 UTC

Parallelism

70/100

Blocked

44%

Avg conflicts / tx

0.4

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,179,836  ·  20 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

0xb44564d6…bb43

0x34b655…2a6f

4 touches
1 conflict

0x987aeb55…0e2a

0xa6afd3…d132

4 touches
1 conflict

0x85631114…3ff6

0xa6afd3…d132

4 touches
1 conflict

0x00000000…003d

0x065c9d…c394

4 touches
1 conflict

0x00000000…003d

0xa6afd3…d132

4 touches
1 conflict

0xfaef08b1…0696

0x34b655…2a6f

4 touches
1 conflict

0xd98b3c10…67b8

0x34b655…2a6f

4 touches
1 conflict

0xcb89a818…e7c1

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

1 conflict on slot 0xb44564d6a3…0fbb43

← previous block·next block →recent activity