← previous blocknext block →recent activity

Analyzing

Block #85,129,840

22 transactions · 20 stateful · 2026-07-02 14:27:05 UTC

Parallelism

73/100

Blocked

45%

Avg conflicts / tx

0.95

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,129,840  ·  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

0xfaef08b1…0696

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

10 touches
10 conflicts

0xe47478a3…a058

0x34b655…2a6f

6 touches
3 conflicts

0x5169bd9f…690b

0x34b655…2a6f

6 touches
3 conflicts

0x548145a9…cfce

0x34b655…2a6f

6 touches
3 conflicts

0x63d31af4…ef45

0x34b655…2a6f

6 touches
3 conflicts

0x21db15ab…425a

0x34b655…2a6f

6 touches
3 conflicts

0x7c0bdc54…9dde

0x34b655…2a6f

6 touches
3 conflicts

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