← previous blocknext block →recent activity

Analyzing

Block #85,162,956

21 transactions · 15 stateful · 2026-07-02 18:07:46 UTC

Parallelism

76/100

Blocked

47%

Avg conflicts / tx

0.62

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,162,956  ·  21 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

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0x05b18b8f…e055

0x34b655…2a6f

4 touches
1 conflict

0x06aed19e…ca57

0x34b655…2a6f

4 touches
1 conflict

0x084fbbd7…cbc0

0x34b655…2a6f

4 touches
1 conflict

0x1254087a…aa4b

0x34b655…2a6f

4 touches
1 conflict

0x1853f465…3255

0x34b655…2a6f

4 touches
1 conflict

0x38bda735…4436

0x34b655…2a6f

4 touches
1 conflict

0x3ea25e92…a36d

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 0xfaef08b108…f90696

← previous block·next block →recent activity