← previous blocknext block →recent activity

Analyzing

Block #85,197,719

16 transactions · 15 stateful · 2026-07-02 21:59:18 UTC

Parallelism

63/100

Blocked

53%

Avg conflicts / tx

1.19

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,197,719  ·  16 txs across 6 waves  ·  depth 6
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

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

10 touches
10 conflicts

0xa678cd56…4fab

0x34b655…2a6f

6 touches
3 conflicts

0xc824469a…6425

0x34b655…2a6f

6 touches
3 conflicts

0x249476f0…c4e1

0x34b655…2a6f

4 touches
1 conflict

0x4384dd01…4f99

0x34b655…2a6f

4 touches
1 conflict

0x4409a908…bbdd

0x34b655…2a6f

4 touches
1 conflict

0x6bdb9869…7558

0x34b655…2a6f

4 touches
1 conflict

0x7d0e92dc…c19b

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

10 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity