← previous blocknext block →recent activity

Analyzing

Block #85,182,168

21 transactions · 19 stateful · 2026-07-02 20:15:46 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.38

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #85,182,168  ·  21 txs across 7 waves  ·  depth 7
parallel ↔ serial

wave w0

wave w1

wave w2

wave w3

wave w4

wave w5

wave w6

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

14 touches
21 conflicts

0x22e0cc1d…ad0d

0x34b655…2a6f

10 touches
10 conflicts

0x2b111712…0e59

0x34b655…2a6f

10 touches
10 conflicts

0xc778dc14…cf3e

0x34b655…2a6f

10 touches
10 conflicts

0x05a7428b…ddf3

0x34b655…2a6f

10 touches
10 conflicts

0xbfb3a356…8811

0x34b655…2a6f

10 touches
10 conflicts

0x70c0e76b…8b6d

0x34b655…2a6f

8 touches
6 conflicts

0x74fd0a9b…3aaa

0x34b655…2a6f

8 touches
6 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

21 conflicts on slot 0xfaef08b108…f90696

← previous block·next block →recent activity