← previous blocknext block →recent activity

Analyzing

Block #86,794,923

19 transactions · 18 stateful · 2026-07-10 07:36:43 UTC

Parallelism

63/100

Blocked

44%

Avg conflicts / tx

0.95

Longest chain

7 deep

Execution timeline

did this block parallelize well?

view

block #86,794,923  ·  19 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

0x922c7ebd…6600

0xc8689a…ee79

8 touches
6 conflicts

0x1a28e34b…1404

0x34b655…2a6f

8 touches
6 conflicts

0x286711a5…b3bf

0x34b655…2a6f

8 touches
6 conflicts

0x3483ab79…8ed3

0x34b655…2a6f

8 touches
6 conflicts

0x63c900f4…2600

0x34b655…2a6f

8 touches
6 conflicts

0x924bac95…3f39

0x34b655…2a6f

8 touches
6 conflicts

0x9f40a209…1193

0x34b655…2a6f

8 touches
6 conflicts

0xfaef08b1…0696

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: Settlement / Helper

6 conflicts on slot 0x922c7ebd9c…1c6600

← previous block·next block →recent activity