← previous blocknext block →recent activity

Analyzing

Block #85,569,164

26 transactions · 22 stateful · 2026-07-04 15:12:55 UTC

Parallelism

65/100

Blocked

45%

Avg conflicts / tx

1.12

Longest chain

9 deep

Execution timeline

did this block parallelize well?

view

block #85,569,164  ·  26 txs across 9 waves  ·  depth 9
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

wave w7

wave w8

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

0xd98b3c10…67b8

0x34b655…2a6f

14 touches
21 conflicts

0xda46a376…f6a6

0x34b655…2a6f

6 touches
3 conflicts

0x50a88d10…679c

0x34b655…2a6f

6 touches
3 conflicts

0xfaef08b1…0696

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x24ed74ea…a3ff

0x34b655…2a6f

6 touches
3 conflicts

0x45597879…8174

0x34b655…2a6f

4 touches
1 conflict

0x6366e366…b51c

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

21 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity