← previous blocknext block →recent activity

Analyzing

Block #85,169,111

23 transactions · 19 stateful · 2026-07-02 18:48:45 UTC

Parallelism

83/100

Blocked

37%

Avg conflicts / tx

0.48

Longest chain

4 deep

Execution timeline

did this block parallelize well?

view

block #85,169,111  ·  23 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

8 touches
6 conflicts

0x301e1c77…9e30

0x34b655…2a6f

6 touches
3 conflicts

0x13a54fa2…5ae3

0x2a68ba…90c5

6 touches
3 conflicts

0x2c8bf7d9…3cc7

0xc8689a…ee79

6 touches
3 conflicts

0xd06fb4dc…5204

0x34b655…2a6f

6 touches
3 conflicts

0x1ee44d08…7262

0x34b655…2a6f

6 touches
3 conflicts

0x819bf1ac…b3e0

0x34b655…2a6f

4 touches
1 conflict

0x1c32bf61…7899

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

6 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity