← previous blocknext block →recent activity

Analyzing

Block #85,176,114

23 transactions · 22 stateful · 2026-07-02 19:35:22 UTC

Parallelism

78/100

Blocked

36%

Avg conflicts / tx

0.78

Longest chain

5 deep

Execution timeline

did this block parallelize well?

view

block #85,176,114  ·  23 txs across 5 waves  ·  depth 5
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

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

0xcdc1731c…b91a

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

6 touches
3 conflicts

0xb86c9560…f3c8

0x34b655…2a6f

6 touches
3 conflicts

0xb90b583f…409f

0x34b655…2a6f

6 touches
3 conflicts

0xc1aad6e5…9135

0x34b655…2a6f

6 touches
3 conflicts

0xd6418d68…bdc5

0x34b655…2a6f

6 touches
3 conflicts

0xdc8d4ee0…def3

0x34b655…2a6f

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 0xfaef08b108…f90696

← previous block·next block →recent activity