← previous blocknext block →recent activity

Analyzing

Block #85,012,330

22 transactions · 20 stateful · 2026-07-02 01:21:01 UTC

Parallelism

68/100

Blocked

45%

Avg conflicts / tx

0.91

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,012,330  ·  22 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

0x3405238a…68b6

0x34b655…2a6f

10 touches
10 conflicts

0xd98b3c10…67b8

0x34b655…2a6f

8 touches
6 conflicts

0xffc2f21e…b393

0x34b655…2a6f

8 touches
6 conflicts

0x03fb27fd…0c06

0x34b655…2a6f

6 touches
3 conflicts

0x689215bc…f298

0x34b655…2a6f

6 touches
3 conflicts

0x9f40a209…1193

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0x922c7ebd…6600

0xc8689a…ee79

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 0x3405238a6d…6268b6

← previous block·next block →recent activity