← previous blocknext block →recent activity

Analyzing

Block #85,109,142

18 transactions · 17 stateful · 2026-07-02 12:08:37 UTC

Parallelism

67/100

Blocked

47%

Avg conflicts / tx

1.28

Longest chain

6 deep

Execution timeline

did this block parallelize well?

view

block #85,109,142  ·  18 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

0xd98b3c10…67b8

0x34b655…2a6f

12 touches
15 conflicts

0xcfa965cc…6fcf

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

0x34b655…2a6f

8 touches
6 conflicts

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0xa0efa7bc…8b24

0x34b655…2a6f

8 touches
6 conflicts

0xaa48195d…ffee

0x34b655…2a6f

8 touches
6 conflicts

0xf324b405…ca30

0x34b655…2a6f

8 touches
6 conflicts

0xf4f4af3b…c5bd

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

15 conflicts on slot 0xd98b3c102b…ca67b8

← previous block·next block →recent activity