← previous blocknext block →recent activity

Analyzing

Block #85,139,503

43 transactions · 36 stateful · 2026-07-02 15:31:36 UTC

Parallelism

72/100

Blocked

69%

Avg conflicts / tx

2.63

Longest chain

12 deep

Execution timeline

did this block parallelize well?

view

block #85,139,503  ·  43 txs across 12 waves  ·  depth 12
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

wave w9

wave w10

wave w11

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

22 touches
55 conflicts

0xa7a0f82a…13d8

0xd32edf…ff58

13 touches
21 conflicts

0x1d61a1c5…9fe6

0x34b655…2a6f

10 touches
10 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

10 touches
10 conflicts

0x00000000…0019

0x1b6862…e19c

8 touches
6 conflicts

0x00000000…0029

0x1b6862…e19c

8 touches
6 conflicts

0x84611dd3…b342

0x1b6862…e19c

8 touches
6 conflicts

0xd9f18d9a…141d

0x1b6862…e19c

8 touches
6 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

55 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity