← previous blocknext block →recent activity

Analyzing

Block #85,184,956

20 transactions · 19 stateful · 2026-07-02 20:34:19 UTC

Parallelism

80/100

Blocked

37%

Avg conflicts / tx

0.55

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,184,956  ·  20 txs across 4 waves  ·  depth 4
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

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

6 touches
3 conflicts

0x48acd99c…3dec

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x379a09c4…259b

0x34b655…2a6f

6 touches
3 conflicts

0x30153288…6d46

0x34b655…2a6f

4 touches
1 conflict

0x3923cd2c…e6d3

0x34b655…2a6f

4 touches
1 conflict

0x51087f5a…61f7

0x34b655…2a6f

4 touches
1 conflict

0xb48d9b07…fa11

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

3 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity